
# Databases & vector on AWS

Compare documented Databases & vector deployments on AWS, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/aws/databases-vector/
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.


## Provider guidance

- Account boundary: AWS account
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://docs.aws.amazon.com/accounts/latest/reference/getting-started.html (checked 2026-11-20).
- Network: VPC
- Identity and access: IAM roles and policies
- Installation guidance: CloudFormation or Terraform; review stack changes and requested IAM permissions.
- Guidance source: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html
- Guidance reviewed: 2026-11-10


### Private offers

AWS Marketplace private offers can contain negotiated pricing and terms for a buyer account. Confirm the product delivery model and your agreement; commitment credit is not established by a directory badge.
Source: https://docs.aws.amazon.com/marketplace/latest/buyerguide/buyer-private-offers-subscribing.html (reviewed 2026-11-14).

### Private connectivity

PrivateLink provides private endpoints to supported services and resources across VPC/account boundaries. Confirm that the selected product exposes a compatible endpoint service.
Source: https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html (reviewed 2026-11-14).

### Cross-account operations

Use an IAM role with scoped permissions and a third-party external ID where applicable. Review the trust principal, support access and revocation separately from installation access.
Source: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html (reviewed 2026-11-14).

### Government environments

AWS GovCloud (US) is a distinct isolated-region environment. A commercial-region product deployment does not establish availability or certification there.
Source: https://docs.aws.amazon.com/govcloud-us/latest/UserGuide/whatis.html (reviewed 2026-11-14).

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

17 listings.


## Apache Doris Self-Hosted

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

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

### Scope and qualifications

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

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

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


### Category fit

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

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

### Deployment boundaries


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

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

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


### Cloud deployment evidence

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

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

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


### Community and maintenance

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

Reviewed 2026-11-18.

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

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

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

### Sources

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

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

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

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

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

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

### Licensing sources

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

### Infrastructure sources

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

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

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


### Buyer diligence


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

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


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

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

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

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

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

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

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

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

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

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

- Operating cost estimate: Sources checked — unresolved. Specify ingestion rate, query concurrency, indexes, compression, replica count, FE quorum, BE count, compaction reserve and storage-compute mode. One TB raw data and 100 users do not determine usable replicated storage, IOPS or an HA compute bill. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://doris.apache.org/docs/4.x/install/preparation/env-checking/ (reviewed 2026-11-18). Supporting source: Current AWS Linux EC2 rates; workload/topology still required — https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. Apache Doris 4.1.5-release was published October 15, 2026. This application release is separate from the date/version of Doris Operator. Use stable documentation and verify operator/application compatibility; dev documentation describes unreleased behavior. cloudimg’s Azure guide/plan packages 4.0.6; it is separate from this 4.1.5-release snapshot and the resolved image version. Scope: Apache Doris Self-Hosted: selected customer-operated edition. Source: https://github.com/apache/doris/releases/tag/4.1.5-release (reviewed 2026-11-18). Supporting source: Older Azure packaged application — https://catalogapi.azure.com/offers/cloudimg1647283583153.apache-doris-ubuntu-24-04?api-version=2018-08-01-beta&market=US&language=en.







## ClickHouse BYOC

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

- Listing: https://launchinyourcloud.com/directory/clickhouse/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Vendor-operated BYOC
- Infrastructure IDs: servers
- License: Commercial
- Licensing model: commercial-only
- Installation: Vendor-assisted BYOC onboarding
- Architecture: Vendor control plane; customer data plane
- Operations: ClickHouse operates the BYOC service; the customer owns the cloud environment.
- Product website: https://clickhouse.com/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The vendor lists AWS, Google Cloud and Azure BYOC options. Confirm region availability and commercial requirements during onboarding. This entry does not describe ordinary ClickHouse Cloud hosting. CVE-2026-116366 is a critical unauthenticated network code-execution issue. ClickHouse states that Cloud and BYOC were patched; self-managed fixes are available in 26.3.62.3-lts, 26.8.36.3-lts, 26.9.27.3, and 26.10.3.7.

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

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


### Category fit

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

### Deployment boundaries


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

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

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

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


### Cloud deployment evidence

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


### Sources

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

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

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

### Licensing sources

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

### Infrastructure sources

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


### Buyer diligence


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

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


- Marketplace delivery: Documented. Microsoft Marketplace lists ClickHouse Cloud BYOC as a fully managed service deployed into the customer's own Azure account. This is the Azure BYOC offer, separate from vendor-account ClickHouse Cloud. Scope: ClickHouse Cloud BYOC procurement for Azure; confirm private-offer, region and agreement terms.. Source: https://marketplace.microsoft.com/en-us/product/clickhouse.byoc_clickhouse_cloud?tab=Overview (reviewed 2026-11-21).

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

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

- SCIM provisioning: Not researched.

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

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

- Air-gapped operation: Not researched.

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

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

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.




### Security and lifecycle reviews

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

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




## CockroachDB BYOC

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

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

### Scope and qualifications

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

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

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


### Category fit

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

### Deployment boundaries


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

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

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

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


### Cloud deployment evidence

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


### Sources

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

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

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

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

### Licensing sources

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

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

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

### Infrastructure sources

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


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

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

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

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

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

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

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Couchbase Server Enterprise Edition

Self-managed distributed NoSQL database deployed in customer-controlled Kubernetes with the Couchbase Operator.

- Listing: https://launchinyourcloud.com/directory/couchbase-server-enterprise/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial subscription for Couchbase Server Enterprise Edition; Community Edition is separately licensed.
- Licensing model: commercial-only
- Installation: Couchbase Kubernetes Operator by Helm or downloaded package, then CouchbaseCluster resources for Enterprise Edition
- Architecture: Customer-operated Couchbase Server pods, Kubernetes Operator, services and persistent volumes
- Operations: Customer manages Kubernetes, storage, networking, security, backups and upgrade policy; the Operator automates database lifecycle operations.
- Product website: https://www.couchbase.com/products/server/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

The current Operator supports Couchbase Server Enterprise Edition 7.2 through 8.0 and is certified for Amazon EKS, Microsoft AKS and Google GKE. Couchbase Capella and Community Edition are outside this listing; verify the exact Operator, Server and Kubernetes compatibility matrix.

This entry is limited to Enterprise Edition, which Couchbase documents as a commercial subscription. Community Edition is a separate licensing scope.

Couchbase Server runs as stateful pods with persistent volumes while the in-cluster Operator reconciles Couchbase resources and lifecycle actions.


### Category fit

- databases-vector: Distributed NoSQL database deployed and lifecycle-managed in customer-controlled Kubernetes clusters.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.couchbase.com/operator/current/overview.html (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.couchbase.com/operator/current/overview.html (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.couchbase.com/operator/current/overview.html (checked 2026-11-19). 


### Cloud deployment evidence

- Couchbase Server Enterprise on EKS, AKS and GKE (aws, azure, gcp): https://docs.couchbase.com/operator/current/overview.html
  Couchbase states that the Operator deploys and manages Server Enterprise Edition and is certified for Amazon EKS, Microsoft AKS and Google GKE. Database pods, services and storage run in the customer's cluster; this is not Couchbase Capella.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Edition: Enterprise Edition. Versions: Server 7.2 through 8.0 in the reviewed compatibility matrix.


### Sources

- Couchbase Operator introduction and certified platforms: https://docs.couchbase.com/operator/current/overview.html

- Couchbase Operator prerequisites and supported versions: https://docs.couchbase.com/operator/current/prerequisite-and-setup.html

- Install Couchbase Operator on Kubernetes: https://docs.couchbase.com/operator/current/install-kubernetes.html

- Couchbase Server editions and licensing: https://production.docs.couchbase.com/server/current/introduction/editions.html

- Buyer evidence: sso: https://docs.couchbase.com/server/current/manage/manage-security/configure-saml.html

- Buyer evidence: iac: https://docs.couchbase.com/operator/current/helm-setup-guide.html

- Reviewed deployment artifact reference: https://github.com/couchbase-partners/helm-charts/releases/download/couchbase-operator-2.94.0/couchbase-operator-2.94.0.tgz

- Official chart index and digest: https://couchbase-partners.github.io/helm-charts/index.yaml

### Licensing sources

- https://production.docs.couchbase.com/server/current/introduction/editions.html

### Infrastructure sources

- https://docs.couchbase.com/operator/current/concept-operator.html


### Buyer diligence


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

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


- Marketplace delivery: Sources checked — unresolved. The reviewed deployment and licensing sources did not establish a public cloud-marketplace offer that unambiguously entitles the selected self-hosted edition. Obtain the exact offer ID, seller, delivery artifact and edition terms before treating marketplace procurement as available. Scope: Couchbase Server Enterprise Edition: selected customer-operated edition. Source: https://docs.couchbase.com/operator/current/overview.html (reviewed 2026-11-19).

- Cloud commitment eligibility: Sources checked — unresolved. Customer-cloud deployment or marketplace delivery does not by itself establish cloud-spend commitment eligibility. Confirm the exact offer, billed dimensions, private-offer terms and buyer agreement. Scope: Couchbase Server Enterprise Edition: selected customer-operated edition. Source: https://docs.couchbase.com/operator/current/overview.html (reviewed 2026-11-19).

- Single sign-on: Documented. The current Enterprise Server Web Console supports SAML SSO, with tested Okta and Microsoft Azure AD/Entra ID integrations. Configure metadata, certificate validation, user/group/role mappings and NameID handling. This console authentication does not establish SAML authentication for application SDK or database data-plane clients. Scope: Couchbase Server Enterprise current 8.0-line Web Console; verify older Server and Operator combinations separately. Source: https://docs.couchbase.com/server/current/manage/manage-security/configure-saml.html (reviewed 2026-11-19).

- SCIM provisioning: Sources checked — unresolved. The reviewed sources did not establish a SCIM endpoint or automated user and group lifecycle for this selected edition. SSO, directory authentication or just-in-time account creation would not by themselves establish SCIM. Scope: Couchbase Server Enterprise Edition: selected customer-operated edition. Source: https://docs.couchbase.com/operator/current/overview.html (reviewed 2026-11-19).

- Compliance attestations: Sources checked — unresolved. The reviewed product and deployment sources did not establish an independent compliance attestation whose assessed scope covers this customer-operated edition and its local infrastructure. Obtain the current report and map customer responsibilities. Scope: Couchbase Server Enterprise Edition: selected customer-operated edition. Source: https://docs.couchbase.com/operator/current/overview.html (reviewed 2026-11-19).

- Security controls: Edition-dependent. The Operator manages the Enterprise database inside the customer's Kubernetes boundary. The deployment still requires buyer configuration of TLS, authentication, network policy, storage encryption, backup and Kubernetes access controls. Scope: Couchbase Server Enterprise Edition: selected customer-operated edition. Source: https://docs.couchbase.com/operator/current/prerequisite-and-setup.html (reviewed 2026-11-19).

- Air-gapped operation: Sources checked — unresolved. The reviewed sources did not establish a fully disconnected installation, update and license workflow for this selected edition. Identify required registries, package repositories, telemetry, identity, activation and support endpoints before claiming air-gapped operation. Scope: Couchbase Server Enterprise Edition: selected customer-operated edition. Source: https://docs.couchbase.com/operator/current/overview.html (reviewed 2026-11-19).

- Deployment artifact / IaC: Documented. The official Helm repository publishes couchbase-operator chart 2.94.0 for Operator 2.9.4. The downloaded chart matches its published SHA-256 digest. It can deploy the Operator, admission controller and a CouchbaseCluster; select a compatible licensed Server image and production values separately. Chart and Operator versions are not Couchbase Server release versions. Scope: Public Helm deployment artifact for the Enterprise database; application licence and Server image remain separate. Source: https://docs.couchbase.com/operator/current/helm-setup-guide.html (reviewed 2026-11-19). Deployment artifact: https://github.com/couchbase-partners/helm-charts/releases/download/couchbase-operator-2.94.0/couchbase-operator-2.94.0.tgz. Artifact reference: chart 2.94.0 / Operator 2.9.4; sha256:f08d9f62fa955964ab380129a5206a414a36495c370bcc245309607afcb38c2a. Supporting source: Official chart index and digest — https://couchbase-partners.github.io/helm-charts/index.yaml.

- Minimum footprint / sizing: Documented. The current 8.0 x86 production floor is a 2-GHz two-core AVX2 CPU, 4 GiB physical RAM and 8 GiB block storage per node. The recommendation is four cores, at least 16 GiB RAM and SSDs. Each enabled service adds requirements; replicas, dataset/index size, backups and HA are additional. Scope: Couchbase Server 8.0 x86 per-node baseline; full service topology requires sizing. Source: https://docs.couchbase.com/server/current/install/pre-install.html (reviewed 2026-11-20).

- License pricing: Edition-dependent. Couchbase Server Enterprise Edition requires a commercial subscription. Community Edition is a different product scope; obtain a quote covering the selected nodes, support and Operator use. Scope: Couchbase Server Enterprise Edition: selected customer-operated edition. Source: https://production.docs.couchbase.com/server/current/introduction/editions.html (reviewed 2026-11-19).

- Operating cost estimate: Sources checked — unresolved. No complete dated operating-cost estimate is established. Define provider and region, workload, availability, retention, storage growth, network transfer, support, software entitlement and operating labor before estimating total cost. Scope: Couchbase Server Enterprise Edition: selected customer-operated edition. Source: https://docs.couchbase.com/operator/current/overview.html (reviewed 2026-11-19).

- Release snapshot / cadence: Documented. The current Operator compatibility material covers Couchbase Server Enterprise Edition 7.2 through 8.0. Compatibility is a matrix across Operator, Server and Kubernetes versions; pin the exact supported combination rather than treating the range as one release. Scope: Couchbase Server Enterprise Edition: selected customer-operated edition. Source: https://docs.couchbase.com/operator/current/prerequisite-and-setup.html (reviewed 2026-11-19).







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




## Meilisearch Community Edition

Self-hosted search engine for typo-tolerant full-text, semantic and hybrid retrieval.

- Listing: https://launchinyourcloud.com/directory/meilisearch-community/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: MIT License for Community Edition. Enterprise Edition uses a BUSL license, cannot be freely used in production and requires a commercial agreement for production self-hosting.
- Licensing model: open-source
- Installation: Install the official binary on an AWS EC2 instance, Google Compute Engine VM or DigitalOcean Droplet, then configure a dedicated system user, systemd service, persistent data directory, reverse proxy and HTTPS.
- Architecture: Customer-operated search server with persistent index storage and optional external embedding or language-model integrations
- Operations: Customer manages the VM, operating system, network rules, master key, TLS, persistent indexes, backups, monitoring, capacity and version upgrades.
- Product website: https://www.meilisearch.com/
- Source review: 2026-11-18; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

The reviewed provider guides deploy a customer-operated server rather than a managed Meilisearch service. Meilisearch Cloud is the vendor-recommended production option, but the Community Edition is explicitly available for independent hosting. Community Edition does not include Enterprise-only sharding, so the documented VM paths do not establish a highly available or horizontally sharded topology. Configured remote embedders or LLM providers can receive indexed or query content; user-provided vectors and customer-selected local endpoints can produce a different data boundary. Meilisearch 1.56.1 and 1.55.1 were security maintenance releases; current 1.57.0 includes those fixes. Affected deployments should move to 1.57.0 or an appropriate later supported patch and review the vendor's branch guidance.

This listing is scoped specifically to the MIT-licensed Community Edition. The separately available Enterprise Edition uses a BUSL license, cannot be used freely in production and reserves sharding as its exclusive feature.

Each reviewed cloud guide runs Meilisearch as a persistent Linux service on a customer-owned VM. The customer provisions and sizes the server and storage; these paths are neither serverless nor vendor-managed.


### Category fit

- databases-vector: Application search engine with typo-tolerant full-text search and semantic or hybrid retrieval over vector embeddings.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.meilisearch.com/docs/resources/self_hosting/deployment/aws (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.meilisearch.com/docs/resources/self_hosting/deployment/gcp (checked 2026-11-16). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.meilisearch.com/docs/resources/self_hosting/deployment/digitalocean (checked 2026-11-16). 


### Cloud deployment evidence

- Meilisearch Community Edition on Amazon EC2 (aws): https://www.meilisearch.com/docs/resources/self_hosting/deployment/aws
  The vendor documents a production-oriented installation on a customer AWS EC2 instance, including the official binary installer, dedicated service account, persistent data directory, systemd service and network security. The customer operates the VM and search service; this is separate from Meilisearch Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.

- Meilisearch Community Edition on Google Compute Engine (gcp): https://www.meilisearch.com/docs/resources/self_hosting/deployment/gcp
  The vendor documents a production-oriented installation on a customer Google Compute Engine VM with billing enabled, including the official binary installer, dedicated service account, persistent data directory, systemd service and firewall configuration. The customer operates the VM and search service.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.

- Meilisearch Community Edition on a DigitalOcean Droplet (digitalocean): https://www.meilisearch.com/docs/resources/self_hosting/deployment/digitalocean
  The vendor documents installation on a customer DigitalOcean Droplet using its official binary installer, persistent service configuration and production security steps. This is a customer-operated Droplet, not a managed Meilisearch Cloud deployment.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Community and maintenance

The official repository publishes continuing versioned releases and public contribution workflows, while the vendor maintains a broader catalog of open-source integrations and deployment components.

Reviewed 2026-11-16.

- Upstream project and contribution workflow: https://github.com/meilisearch/meilisearch

- Current upstream releases: https://github.com/meilisearch/meilisearch/releases

- Official open-source project catalog: https://www.meilisearch.com/open-source

### Sources

- AWS EC2 deployment: https://www.meilisearch.com/docs/resources/self_hosting/deployment/aws

- Google Compute Engine deployment: https://www.meilisearch.com/docs/resources/self_hosting/deployment/gcp

- DigitalOcean Droplet deployment: https://www.meilisearch.com/docs/resources/self_hosting/deployment/digitalocean

- Production self-hosting guidance: https://www.meilisearch.com/docs/resources/self_hosting/deployment/running_production

- Full-text, semantic, hybrid and vector-search capabilities: https://www.meilisearch.com/docs/getting_started/features

- Community and Enterprise edition boundaries: https://www.meilisearch.com/docs/resources/self_hosting/enterprise_edition

- Community Edition MIT license: https://github.com/meilisearch/meilisearch/blob/main/LICENSE

- Meilisearch v1.57.0 release: https://github.com/meilisearch/meilisearch/releases/tag/v1.57.0

- Meilisearch v1.56.1 security release: https://github.com/meilisearch/meilisearch/releases/tag/v1.56.1

- Meilisearch v1.55.1 security release: https://github.com/meilisearch/meilisearch/releases/tag/v1.55.1

### Licensing sources

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

- https://www.meilisearch.com/docs/resources/self_hosting/enterprise_edition

### Infrastructure sources

- https://www.meilisearch.com/docs/resources/self_hosting/deployment/aws

- https://www.meilisearch.com/docs/resources/self_hosting/deployment/gcp

- https://www.meilisearch.com/docs/resources/self_hosting/deployment/digitalocean


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Explicitly unsupported. The vendor comparison explicitly excludes SAML/OIDC SSO from self-hosted open source and places it in Enterprise. The Community engine’s API keys and tenant tokens are not an organization SSO integration. Scope: Self-hosted open-source/Community tier in the vendor comparison. Source: https://www.meilisearch.com/oss-to-cloud (reviewed 2026-11-16).

- SCIM provisioning: Not researched.

- Compliance attestations: Documented. The vendor comparison explicitly excludes the vendor’s SOC 2 Type II offering from self-hosted open source. Hosted-service assurance does not transfer to a customer-operated Community installation; assess the operator’s environment separately. Scope: Vendor SOC 2 offering versus customer-operated Community engine; not a claim that an operator cannot obtain its own attestation. Source: https://www.meilisearch.com/oss-to-cloud (reviewed 2026-11-16).

- Security controls: Documented. Self-hosted Meilisearch uses a master key of at least 16 bytes and scoped API keys for requests. Keep master/admin keys off public frontends and use a search-scoped key where appropriate. This API authorization does not establish SSO or SCIM. Current advisory review: Meilisearch 1.56.1 and 1.55.1 identify important security fixes and urge affected users to upgrade; 1.57.0 includes those fixes. Upgrade to 1.57.0 or a later supported release, or the applicable fixed patch for a maintained branch. Scope: Self-hosted search engine API authorization; not Meilisearch Cloud account SSO Upstream 1.55 and 1.56 maintenance lines; the release notes do not provide one consolidated affected-version range.. Source: https://github.com/meilisearch/meilisearch/releases/tag/v1.56.1 (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://www.meilisearch.com/docs/resources/self_hosting/security/basic_security. Supporting source: v1.55.1 security release — https://github.com/meilisearch/meilisearch/releases/tag/v1.55.1. Supporting source: v1.57.0 — https://github.com/meilisearch/meilisearch/releases/tag/v1.57.0.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The VM guides install an upstream binary, dedicated system user and systemd service, with persistent data and HTTPS/reverse-proxy configuration. Release assets are versioned separately from any cloud image; choose a platform-compatible Community Edition asset. Scope: Community Edition VM installation; not Meilisearch Cloud or Enterprise. Source: https://www.meilisearch.com/docs/resources/self_hosting/deployment/aws (reviewed 2026-11-16). Supporting source: Versioned upstream release assets — https://github.com/meilisearch/meilisearch/releases/tag/v1.57.0.

- Minimum footprint / sizing: Sources checked — unresolved. The indexing guide ties memory and disk use to document fields, payload sizes and batch size. It warns that large payloads can exhaust RAM. The reviewed guide provides tuning guidance, not a universal production CPU/RAM minimum. Scope: Self-hosted indexing workload guidance; capacity requires representative data and benchmarks. Source: https://www.meilisearch.com/blog/indexing-optimization-guide (reviewed 2026-11-16).

- License pricing: Documented. This listing is scoped specifically to the MIT-licensed Community Edition. The separately available Enterprise Edition uses a BUSL license, cannot be used freely in production and reserves sharding as its exclusive feature. Scope: Meilisearch Community Edition: software license terms; infrastructure and operating costs are separate. Source: https://github.com/meilisearch/meilisearch/blob/main/LICENSE (reviewed 2026-11-16). Supporting source: Edition and license conditions — https://www.meilisearch.com/docs/resources/self_hosting/enterprise_edition.

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Meilisearch v1.57.0 was published November 16, 2026, and includes the fixes from the 1.56.1 and 1.55.1 security maintenance releases. Scope: Upstream Meilisearch Community release. Source: https://github.com/meilisearch/meilisearch/releases/tag/v1.57.0 (reviewed 2026-11-18). Supporting source: v1.56.1 security release — https://github.com/meilisearch/meilisearch/releases/tag/v1.56.1. Supporting source: v1.55.1 security release — https://github.com/meilisearch/meilisearch/releases/tag/v1.55.1.




### Security and lifecycle reviews

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

- Meilisearch November 2026 security maintenance (security-advisory): Meilisearch 1.56.1 and 1.55.1 identify important security fixes and urge affected users to upgrade; 1.57.0 includes those fixes. Scope: Upstream 1.55 and 1.56 maintenance lines; the release notes do not provide one consolidated affected-version range. Conditions: Applicability depends on the installed branch and the fixes listed in its release notes. Action: Upgrade to 1.57.0 or a later supported release, or the applicable fixed patch for a maintained branch. Source: https://github.com/meilisearch/meilisearch/releases/tag/v1.56.1; reviewed 2026-11-18. Supporting source: v1.55.1 security release — https://github.com/meilisearch/meilisearch/releases/tag/v1.55.1. Supporting source: v1.57.0 — https://github.com/meilisearch/meilisearch/releases/tag/v1.57.0.




## Milvus

Vector database for similarity search and retrieval over embedding collections.

- Listing: https://launchinyourcloud.com/directory/milvus/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Milvus.
- Licensing model: open-source
- Installation: Run the official standalone Docker or versioned Docker Compose deployment; distributed deployments have separate operational requirements.
- Architecture: Customer-operated vector database and persistent storage, with deployment-specific metadata and write-ahead-log services
- Operations: Customer manages persistent volumes, collections, indexes, access controls, capacity, backups and upgrades.
- Product website: https://milvus.io/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

Current installation scripts can track a different image than a selected stable release; use versioned configurations for reproducibility. Model inference and embedding generation are separate workloads. Managed Zilliz offerings are outside this listing.

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

Customer-operated vector database and persistent storage, with deployment-specific metadata and write-ahead-log services. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- databases-vector: Vector database for approximate nearest-neighbor retrieval over embeddings and associated metadata.

- ai-tools: Embedding storage and vector retrieval infrastructure for AI search and RAG applications.

### Deployment boundaries


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

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

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


### Cloud deployment evidence

- Milvus deployment on Amazon EKS (aws): https://milvus.io/docs/eks.md
  Official instructions provision Amazon EKS and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Milvus deployment on Azure Kubernetes Service (azure): https://milvus.io/docs/azure.md
  Official instructions provision Azure Kubernetes Service and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Milvus deployment on Google Kubernetes Engine (gcp): https://milvus.io/docs/gcp.md
  Official instructions provision Google Kubernetes Engine and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Milvus documents governance under the LF AI & Data Foundation with Zilliz as a major contributor. Its public release stream records continuing October 2026 maintenance.

Reviewed 2026-11-10.

- Foundation and contributing community: https://github.com/milvus-io/milvus

- Current release maintenance: https://github.com/milvus-io/milvus/releases

### Sources

- Official installation and runtime: https://milvus.io/docs/install_standalone-docker.md

- Upstream project and capabilities: https://github.com/milvus-io/milvus

- Current upstream license: https://github.com/milvus-io/milvus/blob/master/LICENSE

### Licensing sources

- https://github.com/milvus-io/milvus/blob/master/LICENSE

### Infrastructure sources

- https://milvus.io/docs/install_standalone-docker.md


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The current core authentication guide uses username/password credentials and SDK token fields with explicitly enabled authorization. It does not establish native SAML/OIDC federation or automatic IdP/group mapping. Hosted Zilliz console SSO is a different deployment; confirm an upstream integration before relying on it. Scope: Self-hosted Milvus core user authentication; federation unresolved. Source: https://milvus.io/docs/authenticate.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official standalone Docker guide links a script fetched from master. Its image selection moves and its upgrade command does not validate arbitrary version transitions; inspect the script and use matching versioned Compose when required. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://milvus.io/docs/install_standalone-docker.md (reviewed 2026-11-14). Deployment artifact: https://raw.githubusercontent.com/milvus-io/milvus/master/scripts/standalone_embed.sh. Artifact reference: master script (moving; inspect its selected image).

- Minimum footprint / sizing: Documented. The standalone requirements specify 8 GB RAM, recommend 16 GB and recommend at least 4 CPU cores with a supported SIMD instruction set. Dataset/index size and storage performance govern actual resources; distributed requirements differ. Scope: Milvus 3.0.x standalone requirements as reviewed. Source: https://milvus.io/docs/prerequisite-docker.md (reviewed 2026-11-14).

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

- Operating cost estimate: Not researched.

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







## Neo4j Self-Managed

Self-managed graph database available in open-source Community and commercial Enterprise editions.

- Listing: https://launchinyourcloud.com/directory/neo4j-self-managed/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: GPLv3 Community Edition; Enterprise Edition uses a commercial Neo4j license.
- Licensing model: open-source
- Installation: Official Helm charts on EKS, AKS or GKE; cloud marketplace and VM options also exist
- Architecture: Customer-operated standalone or clustered graph database servers with persistent volumes
- Operations: Customer manages compute, storage, networking, security, backups, monitoring, capacity and upgrades.
- Product website: https://neo4j.com/
- Source review: 2026-11-18; cloud review: 2026-11-14; licensing review: 2026-11-14; infrastructure review: 2026-11-14

### Scope and qualifications

Community Edition is designed for standalone deployments. Clustering, advanced security and online backup features require Enterprise Edition. This entry does not cover the managed Neo4j Aura service. Deployments that install Graph Data Science should use GDS 2026.10.2 or later, which moves Guava to 33.7.2 for CVE-2026-102554. The advisory concerns attacker-controlled Java deserialization in GDS's dependency; it does not establish that core Neo4j or a default deployment exposes the vulnerable path.

Neo4j Community Edition is GPLv3. Enterprise Edition is commercially licensed and adds clustering, advanced security and operational capabilities.

Neo4j runs persistent standalone or clustered database servers with attached storage. Kubernetes and cloud placement do not remove state, backup or upgrade responsibilities.


### Category fit

- databases-vector: Provides a graph database with Cypher queries, graph traversal and vector-index capabilities in customer-operated deployments.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://neo4j.com/docs/operations-manual/current/kubernetes/ (checked 2026-11-14). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://neo4j.com/docs/operations-manual/current/kubernetes/ (checked 2026-11-14). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://neo4j.com/docs/operations-manual/current/kubernetes/ (checked 2026-11-14). 


### Cloud deployment evidence

- Neo4j Helm deployments on EKS, AKS and GKE (aws, azure, gcp): https://neo4j.com/docs/operations-manual/current/kubernetes/
  Neo4j's Operations Manual documents standalone and clustered Helm deployments on Amazon EKS, Microsoft AKS and Google GKE. Edition and license requirements differ between standalone Community and clustered Enterprise deployments.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.


### Community and maintenance

The upstream open-source project documents its public contribution process and sustained participation from multiple contributors. Vendor release notes record database 2026.10.2 on November 6, 2026, establishing current maintenance. This evidence concerns the project and database release history; it does not make Enterprise-only clustering, backup or bundled tools part of the Community license.

Reviewed 2026-11-14.

- Reviewed maintenance release 2026.10.2: https://neo4j.com/release-notes/database/neo4j-2026102/

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

- Open-source project and contributor participation: https://neo4j.com/open-source-project/

### Sources

- Self-managed editions: https://neo4j.com/docs/operations-manual/current/introduction/

- Kubernetes deployments: https://neo4j.com/docs/operations-manual/current/kubernetes/

- Cloud deployment options: https://neo4j.com/docs/operations-manual/current/cloud-deployments/

- Open-source project and contributor participation: https://neo4j.com/open-source-project/

- Neo4j 2026.10.2 release notes: https://neo4j.com/release-notes/database/neo4j-2026102/

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

- Graph Data Science 2026.10.2 release notes: https://neo4j.com/release-notes/gds/graph-data-science-2026-10-2/

- Guava CVE-2026-102554 advisory: https://github.com/advisories/GHSA-xxph-c9ww-hj94

### Licensing sources

- https://neo4j.com/open-source-project/

- https://neo4j.com/docs/operations-manual/current/introduction/

### Infrastructure sources

- https://neo4j.com/docs/operations-manual/current/kubernetes/

- https://neo4j.com/docs/operations-manual/current/introduction/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Edition-dependent. Neo4j documents OIDC single sign-on for Enterprise Edition, including role mapping and multiple providers. The server must be able to reach its identity provider; this is not a Community Edition entitlement. Scope: Self-managed Neo4j Enterprise Edition. Source: https://neo4j.com/docs/operations-manual/current/authentication-authorization/sso-integration/ (reviewed 2026-11-14).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. Current advisory review: Graph Data Science 2026.10.2 upgrades Guava to 33.7.2 to fix CVE-2026-102554, an uncontrolled-memory-allocation issue during attacker-controlled Java deserialization. Use GDS 2026.10.2 or later and assess whether any Java-deserialization path is exposed. Scope: Guava 4.0 through 33.7.1 is affected and 33.7.2 is fixed. Neo4j does not identify which earlier GDS releases expose the path or claim that core Neo4j is affected.. Source: https://github.com/advisories/GHSA-xxph-c9ww-hj94 (reviewed 2026-11-18). Supporting source: GDS 2026.10.2 notes — https://neo4j.com/release-notes/gds/graph-data-science-2026-10-2/.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor publishes Helm charts and values for a Kubernetes cluster, including an Enterprise three-member example and cloud storage classes. Enterprise requires licence acceptance; select compatible chart/database versions and configure secrets, volumes and backups. Scope: Official Enterprise cluster Helm deployment. Source: https://neo4j.com/docs/operations-manual/current/kubernetes/quickstart-cluster/create-value-file/ (reviewed 2026-11-20). Deployment artifact: https://github.com/neo4j/helm-charts. Artifact reference: Choose compatible chart and Neo4j versions.

- Minimum footprint / sizing: Documented. The current Helm guide enforces at least 0.5 CPU and 2 GB memory per Neo4j instance and shows a three-member Enterprise cluster. These are deployment floors, not production sizing for a dataset. Graph/index size, page cache, query memory, storage and failure headroom require separate sizing. Scope: Helm per-instance floor; cluster and workload capacity not validated. Source: https://neo4j.com/docs/operations-manual/current/kubernetes/quickstart-cluster/create-value-file/ (reviewed 2026-11-20).

- License pricing: Documented. The vendor separates Community GPLv3 terms from the self-managed Enterprise Software Agreement and commercial support terms. Enterprise clustering/features require the corresponding entitlement; do not apply Aura hosted per-GB rates or the Community licence to an Enterprise deployment. Obtain a self-managed quote. Scope: Self-managed Community versus commercial Enterprise licensing. Source: https://neo4j.com/licensing/ (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Neo4j 2026.10.2 was released November 6, 2026. Its compatible Graph Data Science 2026.10.2 component upgrades Guava to 33.7.2 for CVE-2026-102554; that conditional component finding is not a core DBMS claim. Scope: Neo4j Database and optional Graph Data Science 2026.10.2. Source: https://neo4j.com/release-notes/database/neo4j-2026102/ (reviewed 2026-11-18). Supporting source: GDS 2026.10.2 — https://neo4j.com/release-notes/gds/graph-data-science-2026-10-2/.




### Security and lifecycle reviews

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

- Neo4j Graph Data Science Guava denial-of-service dependency (security-advisory): Graph Data Science 2026.10.2 upgrades Guava to 33.7.2 to fix CVE-2026-102554, an uncontrolled-memory-allocation issue during attacker-controlled Java deserialization. Scope: Guava 4.0 through 33.7.1 is affected and 33.7.2 is fixed. Neo4j does not identify which earlier GDS releases expose the path or claim that core Neo4j is affected. Conditions: Requires the optional GDS component and a reachable attacker-controlled Java-deserialization path. Action: Use GDS 2026.10.2 or later and assess whether any Java-deserialization path is exposed. Source: https://github.com/advisories/GHSA-xxph-c9ww-hj94; reviewed 2026-11-18. Supporting source: GDS 2026.10.2 notes — https://neo4j.com/release-notes/gds/graph-data-science-2026-10-2/.




## PostgreSQL

Relational database server for transactional applications and structured SQL workloads.

- Listing: https://launchinyourcloud.com/directory/postgresql/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: PostgreSQL License, a permissive OSI-approved open-source license.
- Licensing model: open-source
- Installation: Install supported operating-system binary packages or build the official source distribution on customer-operated hosts.
- Architecture: Customer-operated PostgreSQL database processes with persistent database files
- Operations: Customer manages database users, network access, storage, backups, replication, query tuning and supported-version updates.
- Product website: https://www.postgresql.org/
- Source review: 2026-11-15; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

This listing covers the upstream database rather than a managed cloud database service. Extensions, administration tools and third-party distributions have separate compatibility and licensing requirements. The 2026-11-12 security update fixes 52 vulnerabilities and requires operators to review several post-update actions, including conditional reindexing and taking a new full backup before subsequent incremental backups. PostgreSQL 14.25 is the final PostgreSQL 14 release; PostgreSQL 14 is end-of-life and should be upgraded to a supported major version.

PostgreSQL License, a permissive OSI-approved open-source license. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated PostgreSQL database processes with persistent database files. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- databases-vector: General-purpose relational database with SQL, transactions and extensibility. Vector similarity search requires a separately selected extension; this listing does not imply built-in vector functionality.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-databases-postgresql-ec2/introduction.html (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/overview-postgres-choose-server-options (checked 2026-11-12). 


### Cloud deployment evidence

- Self-managed PostgreSQL migration to Amazon EC2 (aws): https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-databases-postgresql-ec2/introduction.html
  AWS documents rehosting PostgreSQL on EC2 with the customer retaining database operations. This is separate from Amazon RDS for PostgreSQL.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.

- PostgreSQL on Azure VMs versus managed PostgreSQL (azure): https://learn.microsoft.com/en-us/azure/postgresql/configure-maintain/overview-postgres-choose-server-options
  Microsoft explicitly documents PostgreSQL on customer-managed Azure VMs, including customer responsibility for patching, availability and backups. This listing does not claim the managed Flexible Server service.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Long-running PostgreSQL Global Development Group project with a named community core team, yearly major releases and a documented security/minor-release support policy.

Reviewed 2026-11-10.

- Community core team: https://www.postgresql.org/developer/core/

- Release maintenance and support policy: https://www.postgresql.org/support/versioning/

### Sources

- Official installation and runtime: https://www.postgresql.org/docs/current/install-binaries.html

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

- Current upstream license: https://www.postgresql.org/about/licence/

- PostgreSQL November 2026 security update and PostgreSQL 14 EOL: https://www.postgresql.org/about/news/postgresql-187-1712-1616-1520-1425-and-19-rc-2-released-3442/

### Licensing sources

- https://www.postgresql.org/about/licence/

### Infrastructure sources

- https://www.postgresql.org/docs/current/install-binaries.html


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The server supports GSSAPI automatic authentication, including Kerberos service principals, when built with GSSAPI support. Clients, realms and principal mapping must be configured. This is database-client single sign-on, not an administrative web portal or a SAML assertion endpoint. Scope: PostgreSQL database-client GSSAPI/Kerberos authentication. Source: https://www.postgresql.org/docs/current/gssapi-auth.html (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream installation guide directs operators to platform-specific binary packages or source installation. Packaging depends on operating system and release; authentication, storage, replication and backup configuration are separate. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://www.postgresql.org/docs/current/install-binaries.html (reviewed 2026-11-14).

- Minimum footprint / sizing: Sources checked — unresolved. The installation requirements specify build dependencies and supported platforms, not a workload-independent production CPU/RAM minimum. Size connections, query memory, indexes, WAL, backups and HA replicas against the workload; a successful source build does not establish 100-user or 1-TB capacity. Scope: Upstream build requirements; numeric production sizing unresolved. Source: https://www.postgresql.org/docs/current/install-requirements.html (reviewed 2026-11-20).

- License pricing: Documented. PostgreSQL uses the permissive PostgreSQL License and permits use and distribution without a software fee under its conditions. Commercial support, extensions and managed distributions have separate terms; infrastructure and operating labour are additional. Scope: Upstream PostgreSQL server licence. Source: https://www.postgresql.org/about/licence/ (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The project targets a major release about annually and minor fixes at least quarterly, with urgent fixes outside that schedule. Major versions are supported for five years. Scope: PostgreSQL upstream release/support policy; not a cloud vendor managed-service policy. Source: https://www.postgresql.org/support/versioning/ (reviewed 2026-11-14).







## QuestDB Open Source Self-Hosted

Apache-licensed time-series database installed on customer virtual machines in AWS, Azure or Google Cloud.

- Listing: https://launchinyourcloud.com/directory/questdb-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: QuestDB Open Source is Apache License 2.0; QuestDB Enterprise is separately proprietary.
- Licensing model: open-source
- Installation: Vendor AWS OSS AMI 10.1.0, or customer VM binary/systemd/container installation; validate the AMI OS lifecycle; Azure Marketplace packaging is Enterprise
- Architecture: Persistent QuestDB process with dedicated data disks, network endpoints and customer-managed operating system.
- Operations: Customer manages VM and OS, data disks, networking, authentication, backups, monitoring, upgrades and capacity.
- Product website: https://questdb.com/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

QuestDB Open Source excludes native replication, automatic failover and OIDC SSO in the vendor edition matrix. The requested native HA scenario therefore requires a different edition or a separately validated external design. Azure Marketplace packaging is Enterprise, not OSS. The separate free upstream AWS OSS AMI is confirmed, but its Marketplace OS label is Amazon Linux 2, whose standard support ended June 30, 2026. Resolve the actual AMI and maintained OS before production.

QuestDB Open Source is Apache-2.0. QuestDB Enterprise uses separate commercial terms.

QuestDB runs as a persistent database process on provisioned compute with durable data disks.


### Category fit

- databases-vector: Provides a high-performance time-series database with SQL and ingestion protocols on customer infrastructure.

- data-analytics: Supports time-series ingestion, SQL analytics and operational analysis of large event datasets.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://questdb.com/docs/deployment/aws/ (checked 2026-11-18). Source: https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6 (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://questdb.com/docs/deployment/azure/ (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://questdb.com/docs/deployment/gcp/ (checked 2026-11-18). 


### Cloud deployment evidence

- QuestDB on AWS (aws): https://questdb.com/docs/deployment/aws/
  QuestDB documents manual installation of the full OSS application on customer EC2 with VPC, persistent storage and operating choices. Enterprise marketplace features are not inherited.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- QuestDB on Azure (azure): https://questdb.com/docs/deployment/azure/
  The Azure guide includes customer VM deployment. Its Marketplace offer is Enterprise; use the manual OSS path for this listing and do not transfer Enterprise entitlements.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- QuestDB on Google Cloud (gcp): https://questdb.com/docs/deployment/gcp/
  QuestDB documents deployment to customer Compute Engine with separate durable storage.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- Vendor-published QuestDB Open Source AWS AMI (aws): https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6
  The QuestDB-published AMI installs the OSS database on customer EC2. Package 10.1.0 lists Amazon Linux 2; verify the resolved image and replace unsupported OS packaging. Availability does not supply Enterprise HA, OIDC or a support entitlement.
  Source type: marketplace-offer; reviewed: 2026-11-18; vendor support: not-assessed. Edition: QuestDB Open Source. Versions: AMI package 10.1.0.


### Community and maintenance

QuestDB maintains an open source repository with contributor participation, installation instructions and current OSS releases. Enterprise customer stories do not establish OSS entitlements or customer-account hosting; provider-specific manual guides supply that evidence.

Reviewed 2026-11-18.

- Official maintenance and adoption evidence: https://github.com/questdb/questdb

- Official maintenance and adoption evidence: https://github.com/questdb/questdb/releases/tag/10.2.0

### Sources

- Deploy QuestDB on AWS: https://questdb.com/docs/deployment/aws/

- Deploy QuestDB on Azure: https://questdb.com/docs/deployment/azure/

- Deploy QuestDB on Google Cloud: https://questdb.com/docs/deployment/gcp/

- QuestDB repository and license: https://github.com/questdb/questdb

- Exact vendor AWS OSS AMI and package: https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6

- Amazon Linux 2 lifecycle: https://aws.amazon.com/amazon-linux-2/faqs/

### Licensing sources

- https://github.com/questdb/questdb

- https://questdb.com/terms/

### Infrastructure sources

- https://questdb.com/docs/deployment/aws/

- https://questdb.com/docs/deployment/azure/

- https://questdb.com/docs/deployment/gcp/


### Buyer diligence


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

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


- Marketplace delivery: Documented. QuestDB publishes the free QuestDB Open Source AMI prodview-cddeafdirexw6 on AWS Marketplace, package 10.1.0, x86. Infrastructure is charged separately. The offer lists Amazon Linux 2.0.20210318.0; AWS ended AL2 standard support on June 30, 2026. Verify the resolved AMI OS and use a maintained image before production. This offer is distinct from Azure Enterprise packaging and does not add OSS replication, HA or OIDC. Scope: Vendor-published QuestDB Open Source AWS AMI 10.1.0; package availability is not a production recommendation. Source: https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6 (reviewed 2026-11-18). Supporting source: Manual customer EC2 installation — https://questdb.com/docs/deployment/aws/. Supporting source: Amazon Linux 2 end of support — https://aws.amazon.com/amazon-linux-2/faqs/. Offer prodview-cddeafdirexw6: QuestDB; Amazon Machine Image (AMI), x86; package 10.1.0; https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6.

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

- Single sign-on: Explicitly unsupported. QuestDB’s edition comparison assigns OIDC SSO to Enterprise. Open Source has its documented local authentication controls and does not include that Enterprise OIDC feature. An external identity proxy would be a separate architecture. Scope: Native QuestDB Open Source OIDC SSO; Enterprise entitlement is excluded. Source: https://questdb.com/enterprise/ (reviewed 2026-11-18).

- SCIM provisioning: Sources checked — unresolved. The governance comparison does not establish a native OSS SCIM endpoint or user/group deprovisioning operations. Enterprise RBAC/OIDC are not evidence that SCIM is supplied in Open Source. Scope: QuestDB Open Source Self-Hosted: selected customer-operated edition. Source: https://questdb.com/docs/security/governance/ (reviewed 2026-11-18).

- Compliance attestations: Sources checked — unresolved. The current governance material advertises SOC 2 Type 2 while distinguishing Enterprise controls from OSS. No public audit period/system description established that the report covers this customer-operated OSS database and its external encryption/network controls. Obtain the full report and relevant customer-control scope; a footer badge is insufficient. Scope: QuestDB Open Source Self-Hosted: selected customer-operated edition. Source: https://questdb.com/docs/security/governance/ (reviewed 2026-11-18).

- Security controls: Documented. The edition matrix distinguishes OSS controls from Enterprise TLS, RBAC and OIDC. The AWS guide directs operators to change HTTP/PG credentials, disable unused interfaces and restrict source IPs. Design encryption and network boundaries explicitly rather than inheriting Enterprise capabilities. Scope: QuestDB Open Source Self-Hosted: selected customer-operated edition. Source: https://questdb.com/docs/security/governance/ (reviewed 2026-11-18). Supporting source: OSS instance hardening — https://questdb.com/docs/deployment/aws/. Supporting source: Disable Web Console usage telemetry — https://questdb.com/docs/configuration/telemetry/. Supporting source: AMI operating-system support boundary — https://aws.amazon.com/amazon-linux-2/faqs/.

- Air-gapped operation: Sources checked — unresolved. QuestDB documents telemetry.enabled=false, which stops Web Console usage telemetry and removes its Metrics View. Manual binaries are also available. These facts do not validate the complete disconnected OSS lifecycle: confirm a local JRE/artifact supply, restart/configuration, ingest/query clients, updates and backup/recovery. Enterprise offline-trial and backup claims are not inherited by OSS. Scope: QuestDB Open Source Self-Hosted: selected customer-operated edition. Source: https://questdb.com/docs/configuration/telemetry/ (reviewed 2026-11-18). Supporting source: OSS installation and upgrade artifact — https://questdb.com/docs/deployment/aws/.

- Deployment artifact / IaC: Documented. The manual EC2 guide links the versioned QuestDB 10.2.0 no-JRE binary archive and systemd upgrade steps. Supply a compatible JRE and review service configuration. This is an application artifact, not a complete HA Terraform stack. Scope: QuestDB Open Source Self-Hosted: selected customer-operated edition. Source: https://questdb.com/docs/deployment/aws/ (reviewed 2026-11-18). Deployment artifact: https://github.com/questdb/questdb/releases/download/10.2.0/questdb-10.2.0-no-jre-bin.tar.gz. Artifact reference: QuestDB OSS 10.2.0, no-JRE archive.

- Minimum footprint / sizing: Documented. Capacity guidance recommends 8 GB RAM for basic and 32 GB for advanced use, fast local/NVMe storage and workload-specific CPU planning. The edition comparison explicitly excludes replication and automatic failover from OSS, so this listing cannot satisfy the requested native HA design. Scope: QuestDB Open Source Self-Hosted: selected customer-operated edition. Source: https://questdb.com/docs/getting-started/capacity-planning/ (reviewed 2026-11-18). Supporting source: OSS versus Enterprise availability features — https://questdb.com/enterprise/.

- License pricing: Documented. QuestDB Open Source is Apache 2.0 licensed. Enterprise adds commercial capabilities, including replication/HA and OIDC, under separate terms; those features and licence costs are outside this OSS listing. Scope: QuestDB Open Source Self-Hosted: selected customer-operated edition. Source: https://github.com/questdb/questdb (reviewed 2026-11-18). Supporting source: Commercial edition boundary — https://questdb.com/enterprise/.

- Operating cost estimate: Sources checked — unresolved. The requested HA architecture is not supplied by native QuestDB Open Source replication/failover. Decide whether to change edition or separately validate an external recovery design before costing. Then supply ingestion rate, series/cardinality, query concurrency, retained rows, storage compression and recovery objectives. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://questdb.com/enterprise/ (reviewed 2026-11-18). Supporting source: Current AWS Linux EC2 rates; workload/topology still required — https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. QuestDB OSS 10.2.0 was published November 10, 2026. Enterprise release numbers follow a separate line. Pin the OSS binary/container and dependencies; this snapshot does not establish a support SLA or future cadence. The reviewed AWS OSS AMI packages 10.1.0 rather than upstream 10.2.0 and lists AL2; check the actual OS image lifecycle. Scope: QuestDB Open Source Self-Hosted: selected customer-operated edition. Source: https://github.com/questdb/questdb/releases/tag/10.2.0 (reviewed 2026-11-18). Supporting source: Separate AWS OSS package and OS label — https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6. Supporting source: AL2 support ended June 30, 2026 — https://aws.amazon.com/amazon-linux-2/faqs/.




### Security and lifecycle reviews

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

- QuestDB OSS AWS offer lists an operating system past standard support (lifecycle): The reviewed QuestDB OSS AWS AMI package 10.1.0 lists Amazon Linux 2.0.20210318.0. AWS ended AL2 standard support on June 30, 2026. Scope: The OS label of AWS offer prodview-cddeafdirexw6; not all QuestDB versions, manual VM installs or other cloud packages. Conditions: Marketplace metadata can lag the actual AMI. Confirm the resolved image ID and OS before concluding that a deployed instance uses AL2; application version alone does not establish OS maintenance. Action: Verify the actual AMI OS and use maintained operating-system packaging before production. Migrate any confirmed AL2 host under the vendor/provider upgrade procedure and test backup/recovery. Source: https://aws.amazon.com/amazon-linux-2/faqs/; reviewed 2026-11-18. Supporting source: Exact QuestDB OSS offer, package and OS label — https://aws.amazon.com/marketplace/pp/prodview-cddeafdirexw6.




## Redis Software Self-Managed

Commercial Redis Enterprise software installed and operated in the customer's cloud or data center.

- Listing: https://launchinyourcloud.com/directory/redis-software-self-managed/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial Redis Software subscription.
- Licensing model: commercial-only
- Installation: Redis operator on EKS, AKS or GKE; Linux, container and AWS AMI options are also available
- Architecture: Customer-operated Redis Enterprise cluster and operator with persistent data and management services
- Operations: Customer manages cluster infrastructure, networking, persistence, backups, upgrades, monitoring and licensed capacity.
- Product website: https://redis.io/software/
- Source review: 2026-11-17; cloud review: 2026-11-14; licensing review: 2026-11-14; infrastructure review: 2026-11-14

### Scope and qualifications

This entry covers Redis Software and Redis Enterprise for Kubernetes, not Redis Cloud, Azure Managed Redis or the separately licensed Redis Open Source distribution. Confirm operator, Kubernetes and subscription compatibility for the selected release. Redis Software 8.2.6-52 fixes critical Brotli CVE-2026-111497, includes current Redis OSS security fixes, and resolves SAML SSO, S3 backup, Active-Active, certificate, and OCSP problems. Redis database 8.0 reaches end of life on December 1, 2026; migrate databases to a supported feature set before then.

This listing is for Redis Software, a subscription product governed by Redis commercial terms. It does not classify Redis Open Source.

Redis Enterprise runs persistent cluster nodes and an operator inside customer-managed Kubernetes or on customer VMs. It remains a stateful server deployment.


### Category fit

- databases-vector: Provides commercial in-memory data, search and vector capabilities in a customer-operated Redis Enterprise cluster.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://redis.io/docs/latest/operate/kubernetes/reference/supported_k8s_distributions/ (checked 2026-11-14). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://redis.io/docs/latest/operate/kubernetes/reference/supported_k8s_distributions/ (checked 2026-11-14). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://redis.io/docs/latest/operate/kubernetes/reference/supported_k8s_distributions/ (checked 2026-11-14). 


### Cloud deployment evidence

- Redis Software on EKS, AKS and GKE (aws, azure, gcp): https://redis.io/docs/latest/operate/kubernetes/reference/supported_k8s_distributions/
  Redis lists and tests its current Kubernetes operator on Amazon EKS, Microsoft AKS and Google GKE. The customer operates the Kubernetes cluster and Redis Software deployment; Redis Cloud is separate.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.


### Sources

- Redis deployment methods: https://redis.io/deployment/method/

- Redis Enterprise for Kubernetes: https://redis.io/docs/latest/operate/kubernetes/

- Supported Kubernetes distributions: https://redis.io/docs/latest/operate/kubernetes/reference/supported_k8s_distributions/

- Redis Software agreement: https://redis.io/legal/software-agreement/

- Redis Software 8.2.6-52 security and lifecycle notes: https://redis.io/docs/latest/operate/rs/release-notes/rs-8-2-releases/rs-8-2-6-52/

- Redis database and cluster version lifecycle: https://redis.io/docs/latest/operate/rs/8.0/installing-upgrading/product-lifecycle/

### Licensing sources

- https://redis.io/legal/software-agreement/

- https://redis.io/deployment/method/

### Infrastructure sources

- https://redis.io/docs/latest/operate/kubernetes/

- https://redis.io/docs/latest/operate/kubernetes/deployment/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Redis Software supports IdP- and SP-initiated SAML 2.0 for the Cluster Manager UI with role mapping. This is administrative browser identity, not the Redis database client authentication protocol. Scope: Redis Software Cluster Manager UI; not Redis Cloud or Open Source. Source: https://redis.io/docs/latest/operate/rs/security/access-control/saml-sso/ (reviewed 2026-11-14).

- SCIM provisioning: Explicitly unsupported. The Software SAML guide explicitly says SCIM user provisioning is unavailable. It supports just-in-time user creation at first SSO login; JIT is not equivalent to SCIM provisioning/deprovisioning. Scope: Redis Software administrative users. Source: https://redis.io/docs/latest/operate/rs/security/access-control/saml-sso/ (reviewed 2026-11-14).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The official installation guide delivers Redis Software as a vendor package and installation script for supported Linux hosts, followed by cluster/database configuration. Obtain the chosen compatible release and licence. This is a product installer path; operating-system provisioning, node placement and HA design remain separate. Scope: Official Redis Software Linux installation; not Redis Open Source packaging. Source: https://redis.io/docs/latest/operate/rs/installing-upgrading/install/install-on-linux/ (reviewed 2026-11-20). Deployment artifact: https://redis.io/docs/latest/operate/rs/installing-upgrading/install/install-on-linux/. Artifact reference: Select the supported Redis Software release for the target OS.

- Minimum footprint / sizing: Documented. The 7.8 production matrix requires at least three nodes, each with 2 CPU cores and 8 GB RAM; it recommends at least 8 cores/32 GB per node. Ephemeral and persistent storage depend on RAM and persistence/tiering modes. This is Redis Software guidance, not Redis Open Source sizing or capacity for a specified dataset. Scope: Redis Software 7.8 production node floor; workload/tiering sizing additional. Source: https://redis.io/docs/latest/operate/rs/7.8/installing-upgrading/install/plan-deployment/hardware-requirements/ (reviewed 2026-11-20).

- License pricing: Documented. Redis Software uses a cluster licence controlling features and shard capacity; every cluster, including passive/cold DR, needs a separate licence. Trial mode lasts 30 days and permits four shards. Obtain commercial capacity/support pricing; Redis Open Source licensing does not cover this product. Scope: Commercial self-managed Redis Software cluster licensing; no public price quoted. Source: https://redis.io/docs/latest/operate/rs/clusters/configure/license-keys/ (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.




### Security and lifecycle reviews

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

- Redis Software Brotli and dependency patch (security-advisory): Redis Software 8.2.6-52 patches critical Brotli CVE-2026-111497 through updated bundled components. Scope: Redis Software 8.2.6-52; not Redis Cloud or every independently installed Redis Open Source distribution. Conditions: The actual Redis Software image and affected bundled components determine exposure. Redis database and cluster version lifecycles are separate. Action: Apply a compatible Software/operator update; review SAML role mappings, tokens, backup behavior and module-upgrade limitations. Source: https://redis.io/docs/latest/operate/rs/release-notes/rs-8-2-releases/rs-8-2-6-52/; reviewed 2026-11-17.

- Redis database 8.0 support deadline (lifecycle): The bundled Redis database 8.0 STS line reaches end of life on December 1, 2026. Scope: Redis database 8.0 feature set inside Redis Software; this is not the Redis Software 8.0 cluster-version EOL date. Conditions: A database can lose support while its enclosing cluster version remains supported. Contract terms and the selected operator/cluster version need separate checks. Action: Move databases to a supported compatible database version before the deadline; plan the database upgrade separately from the cluster upgrade. Source: https://redis.io/docs/latest/operate/rs/8.0/installing-upgrading/product-lifecycle/; reviewed 2026-11-17.




## ScyllaDB Enterprise Self-Managed

Self-managed distributed NoSQL database deployed on customer-controlled cloud virtual machines.

- Listing: https://launchinyourcloud.com/directory/scylladb-enterprise-self-managed/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: ScyllaDB Source Available License Agreement for current Enterprise releases; eligibility and capacity limits apply unless covered by paid terms.
- Licensing model: source-available
- Installation: Official cloud image/AMI, with a documented AWS CloudFormation cluster example
- Architecture: Customer-operated ScyllaDB nodes with cloud networking and local or attached persistent storage
- Operations: Customer manages topology, networking, authentication, capacity, backups, monitoring, patching and upgrades.
- Product website: https://www.scylladb.com/product/scylla-enterprise/
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Current stable documentation covers ScyllaDB 2026.3 and labels each provider path self-managed, separately from ScyllaDB Cloud. The source-available license is not OSI open source; its free grant has eligibility and aggregate capacity limits, and commercial customers require paid terms.

Current ScyllaDB Enterprise is source-available under ScyllaDB's agreement, not an OSI-approved license. The agreement imposes eligibility, usage and commercial-customer restrictions.

The database runs directly on customer-controlled cloud compute instances; multi-node durability, storage layout and replication are customer-operated.


### Category fit

- databases-vector: Distributed NoSQL wide-column database for high-throughput, low-latency application data.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-azure.html (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-gcp.html (checked 2026-11-19). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-oci.html (checked 2026-11-19). 


### Cloud deployment evidence

- Self-managed ScyllaDB 2026.3 on AWS (aws): https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html
  Official instructions launch ScyllaDB AMIs into the customer's AWS VPC and distinguish this self-managed deployment from ScyllaDB Cloud.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Versions: 2026.3 documentation.

- Self-managed ScyllaDB 2026.3 on Google Cloud (gcp): https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-gcp.html
  Official instructions use the customer's active Google Cloud account and gcloud to launch ScyllaDB images and call the deployment self-managed.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Versions: 2026.3 documentation.

- Self-managed ScyllaDB 2026.3 on Azure (azure): https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-azure.html
  Official instructions use the customer's Azure subscription and resource group to create a ScyllaDB VM and call the deployment self-managed.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Versions: 2026.3 documentation.

- Self-managed ScyllaDB 2026.3 on OCI (oci): https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-oci.html
  Official instructions deploy the bring-your-own-license ScyllaDB Marketplace image into the customer's OCI tenancy, compartment, VCN and compute instance and call the deployment self-managed.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed. Versions: 2026.3 documentation.


### Sources

- Install ScyllaDB 2026.3: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/

- ScyllaDB Enterprise self-managed product: https://www.scylladb.com/product/

- Supported ScyllaDB versions: https://docs.scylladb.com/stable/versioning/version-support.html

- ScyllaDB Source Available License Agreement: https://www.scylladb.com/scylladb-software-license-agreement/

- Buyer evidence: marketplace: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-oci.html

- Buyer evidence: commitments: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html

- Reviewed deployment artifact reference: https://s3.amazonaws.com/downloads.scylladb.com/downloads/scylla/aws/cloudformation/scylla_cluster_2026.3.6_x86_64.yaml

- Buyer evidence: footprint: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-gcp.html

- Source-available licensing FAQ: https://www.scylladb.com/source-available-faq/

### Licensing sources

- https://www.scylladb.com/scylladb-software-license-agreement/

- https://www.scylladb.com/source-available-faq/

### Infrastructure sources

- https://docs.scylladb.com/manual/stable/getting-started/install-scylla/


### Buyer diligence


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

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


- Marketplace delivery: Documented. ScyllaDB documents a bring-your-own-license Marketplace image for self-managed Enterprise deployment in OCI. The other reviewed cloud paths use vendor images or instructions and do not establish equivalent Marketplace offers. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-oci.html (reviewed 2026-11-19).

- Cloud commitment eligibility: Sources checked — unresolved. Customer-cloud deployment or marketplace delivery does not by itself establish cloud-spend commitment eligibility. Confirm the exact offer, billed dimensions, private-offer terms and buyer agreement. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html (reviewed 2026-11-19).

- Single sign-on: Sources checked — unresolved. The reviewed installation and edition sources did not establish the exact SSO protocols, identity-provider support and entitlement for this selected edition. Confirm authentication, role mapping and break-glass access before deployment. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/ (reviewed 2026-11-19).

- SCIM provisioning: Sources checked — unresolved. The reviewed sources did not establish a SCIM endpoint or automated user and group lifecycle for this selected edition. SSO, directory authentication or just-in-time account creation would not by themselves establish SCIM. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/ (reviewed 2026-11-19).

- Compliance attestations: Sources checked — unresolved. The reviewed product and deployment sources did not establish an independent compliance attestation whose assessed scope covers this customer-operated edition and its local infrastructure. Obtain the current report and map customer responsibilities. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/ (reviewed 2026-11-19).

- Security controls: Edition-dependent. The provider guides deploy customer-controlled database nodes and networking. The buyer must explicitly configure authentication, encryption, firewall rules, monitoring, backup and repair; image delivery alone is not a hardened cluster baseline. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/ (reviewed 2026-11-19).

- Air-gapped operation: Sources checked — unresolved. The reviewed sources did not establish a fully disconnected installation, update and license workflow for this selected edition. Identify required registries, package repositories, telemetry, identity, activation and support endpoints before claiming air-gapped operation. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html (reviewed 2026-11-19).

- Deployment artifact / IaC: Documented. The AWS guide links a versioned x86 CloudFormation cluster example for 2026.3.6. It provisions EC2 networking and cluster resources and accepts a regional Scylla AMI. Review its public-address/SSH settings, initial credentials, instance count and licence limits; this sample is not a validated production HA or cost design. Scope: AWS x86 sample stack; ARM templates and other providers have separate images and configuration. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html (reviewed 2026-11-19). Deployment artifact: https://s3.amazonaws.com/downloads.scylladb.com/downloads/scylla/aws/cloudformation/scylla_cluster_2026.3.6_x86_64.yaml. Artifact reference: scylla_cluster_2026.3.6_x86_64.yaml; SHA-256 71c636562d0e5ea54633ba4c0f95a32a1db139726a46923c2372e6550cfb6c7c.

- Minimum footprint / sizing: Documented. The GCP image launch guide requires at least 2 vCPUs. This bootstrap requirement does not establish production node count, RAM, local SSD capacity, HA, replication, compaction or a 1-TB workload design; follow provider-specific sizing and licence limits separately. Scope: ScyllaDB 2026.3 GCP image launch minimum only; not a cluster-wide production footprint. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-gcp.html (reviewed 2026-11-19).

- License pricing: Edition-dependent. The current source-available agreement provides a restricted free grant subject to eligibility and aggregate capacity limits; commercial customers and use beyond those terms require a paid agreement. Validate legal eligibility and capacity calculations. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://www.scylladb.com/scylladb-software-license-agreement/ (reviewed 2026-11-19). Supporting source: Source-available licensing FAQ — https://www.scylladb.com/source-available-faq/.

- Operating cost estimate: Sources checked — unresolved. No complete dated operating-cost estimate is established. Define provider and region, workload, availability, retention, storage growth, network transfer, support, software entitlement and operating labor before estimating total cost. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/launch-on-aws.html (reviewed 2026-11-19).

- Release snapshot / cadence: Documented. The current stable self-managed installation documentation is labeled ScyllaDB 2026.3. Verify the exact patch and its support window before deploying provider images or performing an upgrade. Scope: ScyllaDB Enterprise Self-Managed: selected customer-operated edition. Source: https://docs.scylladb.com/manual/stable/getting-started/install-scylla/ (reviewed 2026-11-19).







## Supabase Self-Hosted

Self-hosted PostgreSQL application backend with authentication, storage, APIs and realtime services.

- Listing: https://launchinyourcloud.com/directory/supabase/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, railway, vultr
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Open-source components with individual licenses; the Supabase platform repository uses Apache-2.0
- Licensing model: open-source
- Installation: Official Docker Compose distribution, community AWS CloudFormation template, Railway project template, or Vultr Marketplace server image
- Architecture: Customer-operated PostgreSQL database and containerized backend services
- Operations: Customer manages provisioning, hardening, database maintenance, scaling, backups and monitoring; self-hosting is community-supported.
- Product website: https://supabase.com/
- Source review: 2026-11-21; cloud review: 2026-11-21; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The self-hosted stack runs as one project. Managed-platform capabilities such as branching, managed backups/PITR and the Management API are not included. The Supabase CLI development stack is not a hardened production deployment. Review each bundled component license.

The listed self-hosted distribution uses open-source components; the Supabase platform repository is Apache-2.0. Managed-cloud features and paid support are separate from this public self-hosted distribution, and bundled components retain their own licenses.

The official installation runs PostgreSQL and supporting services through Docker Compose on a Linux server or VPS. This is persistent application infrastructure, even when it exposes functions.


### Category fit

- backend-platforms: PostgreSQL-based application backend with authentication, APIs, storage, realtime and functions; self-hosting does not include every managed-platform feature.

- databases-vector: A PostgreSQL-based application data platform with database APIs, authentication and storage services. This entry covers the self-hosted stack.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://github.com/supabase-community/supabase-on-aws (checked 2026-11-21). 

- railway: Customer platform workspace; Customer-operated; control plane: not-assessed. Source: https://railway.com/guides/supabase (checked 2026-11-21). 

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


### Cloud deployment evidence

- Supabase community AWS CloudFormation/CDK deployment (aws): https://github.com/supabase-community/supabase-on-aws
  This project-community template deploys Supabase containers on ECS Fargate with Aurora and Studio on Amplify Hosting. It is an alternative to the upstream Compose layout and does not support pg_graphql/GraphQL. Harden Studio access, review feature differences and operate the AWS resources yourself; this is not managed Supabase.
  Source type: community-template; reviewed: 2026-11-21; vendor support: not-assessed.

- Self-host Supabase in a Railway project (railway): https://railway.com/guides/supabase
  Railway documents a community template for PostgreSQL, authentication, REST, storage, and Studio. The services communicate over private networking in the customer’s Railway project. Railway operates the underlying platform.
  Source type: provider-guide; reviewed: 2026-11-21; vendor support: not-assessed.

- Deploy the Supabase Marketplace application on Vultr Compute (vultr): https://docs.vultr.com/how-to-use-vultr-s-supabase-marketplace-application
  Vultr documents selecting the Supabase application while provisioning a Compute server in the customer’s account. The customer chooses the region and plan and administers the installed stack.
  Source type: provider-guide; reviewed: 2026-11-21; vendor support: not-assessed.


### Sources

- Self-hosting scope and responsibilities: https://supabase.com/docs/guides/self-hosting

- Official Docker deployment: https://supabase.com/docs/guides/self-hosting/docker

- Platform repository license: https://raw.githubusercontent.com/supabase/supabase/master/LICENSE

- Self-host Supabase in a Railway project: https://railway.com/guides/supabase

- Deploy the Supabase Marketplace application on Vultr Compute: https://docs.vultr.com/how-to-use-vultr-s-supabase-marketplace-application

### Licensing sources

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

- https://supabase.com/docs/guides/self-hosting

### Infrastructure sources

- https://supabase.com/docs/guides/self-hosting/docker


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The self-hosted Auth service supports external OAuth providers, including a configurable Keycloak issuer. This serves end users of applications built on Supabase; it does not establish organizational SSO for the self-hosted Studio/admin dashboard. Review provider, redirect, signup and administrative access separately. Scope: Self-hosted application-user Auth service; Studio federation excluded. Source: https://raw.githubusercontent.com/supabase/auth/master/README.md (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The upstream docker directory contains the multi-service Compose stack and related environment/configuration files. Follow the self-hosting guide for a matching deployment version and replace secrets. Scope: Self-hosted multi-service stack; not the monthly developer newsletter version. Source: https://github.com/supabase/supabase/blob/master/docker/docker-compose.yml (reviewed 2026-11-14). Deployment artifact: https://github.com/supabase/supabase/blob/master/docker/docker-compose.yml. Artifact reference: master (moving branch).

- Minimum footprint / sizing: Documented. For all components, the guide gives 2 CPU cores, 4 GB RAM and 40 GB SSD as a minimum; 4 cores, 8 GB+ and 80 GB+ SSD are recommended. Optional analytics increases requirements. Scope: Docker stack for development and small-to-medium production; not every workload. Source: https://supabase.com/docs/guides/self-hosting/docker (reviewed 2026-11-14).

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

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## TiDB Community Self-Hosted

Open-source distributed SQL database with customer-operated cloud Kubernetes guides and a separately packaged third-party AWS VM option.

- Listing: https://launchinyourcloud.com/directory/tidb-community/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp, azure, alibaba
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0.
- Licensing model: open-source
- Installation: TiDB Operator and versioned Kubernetes resources on EKS/GKE/AKS; the Alibaba ACK Terraform recipe has older development/test version constraints; optional Techlatest AWS single-VM bundle is separately packaged and does not supply the Operator HA topology
- Architecture: TiDB, PD and TiKV services on customer Kubernetes node pools with persistent storage, or a separately reviewed third-party single-VM bundle; optional analytics and monitoring depend on the deployment.
- Operations: Customer manages the chosen Kubernetes cluster or VM, operating system/node pools, persistent storage, networking, database identities, backups, monitoring, upgrades, scaling and database operations.
- Product website: https://www.pingcap.com/tidb/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

This entry covers TiDB Community, not TiDB Cloud. AKS has a complete current guide even though the deployment FAQ omits it; that difference does not negate the documented path. The ACK guide is an older development/test recipe, while the current FAQ still names ACK. Match operator/database versions and validate production permissions, storage and HA before use. An alternative Techlatest AWS image packages TiDB OSS with Grafana/Prometheus on one VM. Package 1.0.2 does not identify the database components’ versions and is not an HA cluster or PingCAP support entitlement. Do not transfer Operator sizing, offline procedures or the upstream v8.5.8 snapshot to this image.

The TiDB repository is Apache-2.0 licensed. Managed TiDB Cloud services have separate terms.

TiDB runs persistent database/storage services on customer Kubernetes node pools, or as a separately packaged single-VM OSS bundle. The seller VM is not the Operator-based production HA topology.


### Category fit

- databases-vector: Provides a distributed SQL database with horizontally scaled storage and query services.

- data-analytics: Supports scalable transactional and analytical SQL workloads on a customer-operated cluster.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-aws-eks/ (checked 2026-11-18). Source: https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-gcp-gke/ (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-azure-aks/ (checked 2026-11-18). 

- alibaba: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.pingcap.com/tidb-in-kubernetes/v1.4/deploy-on-alibaba-cloud/ (checked 2026-11-18). 


### Cloud deployment evidence

- TiDB on Amazon EKS (aws): https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-aws-eks/
  PingCAP documents customer EKS node pools, storage and TiDB Operator deployment.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- TiDB on Google Kubernetes Engine (gcp): https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-gcp-gke/
  PingCAP documents customer GKE node pools, persistent disks and TiDB Operator deployment.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- TiDB Community on Azure AKS (azure): https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-azure-aks/
  PingCAP provides a full AKS deployment guide with customer node pools, PD/TiKV/TiDB and monitoring manifests. A deployment guide establishes a documented path, not a commercial support contract.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- TiDB on Alibaba Cloud ACK (alibaba): https://docs.pingcap.com/tidb-in-kubernetes/v1.4/deploy-on-alibaba-cloud/
  PingCAP’s v1.4 guide deploys a full cluster into customer ACK using Terraform and TiDB Operator and is scoped to development/testing. The current deployment FAQ still names ACK; old Terraform/image examples need a current-version production review.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed. Versions: TiDB Operator guide v1.4.

- Techlatest TiDB OSS single-VM bundle in customer EC2 (aws): https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html
  The seller guide subscribes to exact AWS offer prodview-ddl3tqewcoko4 and launches into the customer region/VPC/EC2 account. TiDB and its monitoring interfaces run on the VM. This is a separately packaged single-node option, not the Kubernetes HA path; package 1.0.2 leaves embedded database versions unreported. Restrict SSH/RDP and set the documented initial credentials.
  Source type: third-party-package; reviewed: 2026-11-18; vendor support: not-assessed. Edition: Repackaged open-source TiDB bundle. Versions: Seller package 1.0.2; embedded database versions unreported.


### Community and maintenance

PingCAP maintains the Apache-licensed database and operator with public contribution activity and supported LTS releases. Its named customer case-study catalog demonstrates adoption, while TiDB Cloud stories are kept separate from Community cloud evidence.

Reviewed 2026-11-18.

- Official maintenance and adoption evidence: https://github.com/pingcap/tidb/releases/tag/v8.5.8

- Official maintenance and adoption evidence: https://www.pingcap.com/case-studies/

- Official maintenance and adoption evidence: https://docs.pingcap.com/tidb-in-kubernetes/stable/tidb-operator-overview/

### Sources

- TiDB Operator overview: https://docs.pingcap.com/tidb-in-kubernetes/stable/tidb-operator-overview/

- Deploy TiDB on AWS EKS: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-aws-eks/

- Deploy TiDB on Google Cloud GKE: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-gcp-gke/

- TiDB Apache 2.0 license: https://github.com/pingcap/tidb/blob/master/LICENSE

- TiDB Community on Azure AKS: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-azure-aks/

- TiDB on Alibaba Cloud ACK: https://docs.pingcap.com/tidb-in-kubernetes/v1.4/deploy-on-alibaba-cloud/

- Current TiDB deployment FAQ: https://docs.pingcap.com/tidb/stable/deploy-and-maintain-faq/

- Exact third-party TiDB OSS AWS image: https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4

- Seller customer-account VM deployment: https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html

### Licensing sources

- https://github.com/pingcap/tidb/blob/master/LICENSE

### Infrastructure sources

- https://docs.pingcap.com/tidb-in-kubernetes/stable/tidb-operator-overview/

- https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html


### Buyer diligence


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

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


- Marketplace delivery: Documented. Techlatest.net publishes TiDB with Grafana/Prometheus as AWS AMI prodview-ddl3tqewcoko4: a repackaged open-source single-VM bundle, package 1.0.2 on CentOS Stream 9. The reviewed t2.large option charges USD 0.13/hour for seller support plus AWS resources. This is an alternative to the Operator-based Kubernetes path, not that HA topology. The seller does not name embedded TiDB/TiKV/PD versions; inspect and pin them before production rather than inheriting the upstream release snapshot. Scope: Optional third-party TiDB Community VM delivery in the customer AWS account; independent from Operator/Kubernetes topology, package versions and support. Source: https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4 (reviewed 2026-11-18). Supporting source: Seller single-VM installation and initial credentials — https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html. Supporting source: TiDB Community upstream licence — https://github.com/pingcap/tidb/blob/master/LICENSE. Offer prodview-ddl3tqewcoko4: Techlatest.net; Amazon Machine Image (AMI), x86; single-VM bundle; package Seller package 1.0.2; embedded database versions unreported; https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4.

- Cloud commitment eligibility: Sources checked — unresolved. The upstream Community Apache licence has no subscription charge. The alternative Techlatest VM has a separately billed seller-support charge on AWS Marketplace, but its exact commitment eligibility is not established by the offer. Confirm the selected offer/contract and buyer’s AWS agreement; neither the free licence nor TiDB Cloud SaaS terms settle that transaction. Scope: TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope. Source: https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4 (reviewed 2026-11-18). Supporting source: AWS commitment qualification is product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html. Supporting source: Community licence — https://github.com/pingcap/tidb/blob/master/LICENSE.

- Single sign-on: Documented. TiDB Self-Managed v8.5 documents OIDC SSO for the TiDB Dashboard web UI, with Okta, Auth0 and self-hosted Casdoor examples. Dashboard encrypts/stores a SQL account password to complete an impersonated SQL sign-in after OIDC authentication. SQL password rotation requires reauthorization; disabling SSO erases the stored password. This establishes Dashboard sign-in only. A selected SQL client’s federated login and SCIM lifecycle require separate confirmation. Scope: TiDB Community/Self-Managed v8.5 Dashboard web UI, including its documented Kubernetes deployment; SQL-client SSO and the versions inside the third-party VM are assessed separately. Source: https://docs.pingcap.com/tidb/stable/dashboard-session-sso/ (reviewed 2026-11-18). Supporting source: Dashboard access on customer-operated Kubernetes — https://docs.pingcap.com/tidb-in-kubernetes/stable/access-dashboard/. Supporting source: Least-privileged Dashboard SQL users — https://docs.pingcap.com/tidb/stable/dashboard-user/. Supporting source: Protect Dashboard and privileged PD interfaces — https://docs.pingcap.com/tidb/stable/dashboard-ops-security/. Supporting source: Separate SQL JWT/LDAP authentication boundary — https://docs.pingcap.com/tidb/stable/security-compatibility-with-mysql/.

- SCIM provisioning: Sources checked — unresolved. JWT and LDAP authentication do not establish SCIM user/group management or automatic SQL-account deprovisioning. A current Community endpoint and supported operations were not confirmed; review provisioning and token revocation separately. Scope: TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope. Source: https://docs.pingcap.com/tidb/stable/security-compatibility-with-mysql/ (reviewed 2026-11-18).

- Compliance attestations: Sources checked — unresolved. PingCAP’s Trust Hub advertises ISO and SOC assurances and requests certificate/report access. Its specific ISO announcement identifies TiDB Cloud, a managed service, rather than this customer-operated Community cluster. A current certificate/report covering the relevant Community development/support boundary and buyer controls was not established; do not inherit TiDB Cloud attestations. Scope: TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope. Source: https://www.pingcap.com/trust-hub/compliance/ (reviewed 2026-11-18). Supporting source: Explicit TiDB Cloud ISO certification boundary — https://www.pingcap.com/press-release/announcing-iso-27001-certification-for-tidb-cloud/.

- Security controls: Documented. PingCAP documents certificates and TLS between components, plus client TLS and privileged-user/network controls. JWT SQL authentication requires trusted issuer/JWKS configuration and client TLS because the client sends the token through a clear-password plugin. Database token/LDAP authentication alone does not establish SSO or SCIM. Techlatest’s VM guide starts TiDB root with a blank password and Grafana with admin/admin; set new credentials and restrict SSH/RDP before use. Its component patch levels remain unconfirmed. Optional Dashboard OIDC SSO stores an encrypted SQL password for impersonation; use the documented least-privileged account and network/TLS controls, and reauthorize after SQL password rotation. Scope: TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope. Source: https://docs.pingcap.com/tidb/stable/enable-tls-between-components/ (reviewed 2026-11-18). Supporting source: Self-managed security configuration — https://docs.pingcap.com/tidb/stable/best-practices-for-security-configuration/. Supporting source: SQL authentication and JWT TLS requirements — https://docs.pingcap.com/tidb/stable/security-compatibility-with-mysql/. Supporting source: Seller-specific initial credential requirements — https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html. Supporting source: Dashboard OIDC credential-handling boundary — https://docs.pingcap.com/tidb/stable/dashboard-session-sso/. Supporting source: Least-privileged Dashboard SQL users — https://docs.pingcap.com/tidb/stable/dashboard-user/.

- Air-gapped operation: Documented. The Kubernetes guide explicitly describes transferring container images to a server without external network access and loading them locally. Include operator, PD/TiKV/TiDB, optional TiFlash/TiCDC, monitoring and initialization images; its v8.5.7 example is not a complete current-version image lockfile. Scope: Operator-based Kubernetes offline procedure only; the third-party VM’s offline lifecycle is not established. Source: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-general-kubernetes/ (reviewed 2026-11-18).

- Deployment artifact / IaC: Documented. The AKS guide provides a versioned TiDB custom-resource manifest from TiDB Operator v1.6.6, together with separate monitoring/dashboard manifests. The operator version and TiDB image versions are independent; review requests, storage classes and all example defaults. The optional seller VM has a separate AMI/image inventory; do not treat the Operator manifest as its installation artifact. Scope: Operator v1.6.6 Kubernetes manifest; the third-party VM is a separate delivery. Source: https://docs.pingcap.com/tidb-in-kubernetes/stable/deploy-on-azure-aks/ (reviewed 2026-11-18). Deployment artifact: https://raw.githubusercontent.com/pingcap/tidb-operator/v1.6.6/examples/aks/tidb-cluster.yaml. Artifact reference: TiDB Operator v1.6.6 AKS example. Supporting source: Separate single-VM deployment artifact — https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html.

- Minimum footprint / sizing: Documented. The v8.5 production hardware baseline lists two TiDB nodes at 16 cores/48 GB each, three PD at 8 cores/16 GB, and three TiKV at 16 cores/64 GB, plus SSD and network requirements. Optional analytics/changefeed/monitoring add components. These are component recommendations, not exact pod requests or a benchmark for 100 users. The seller’s t2.large VM example is not this production multi-node baseline. Scope: Upstream v8.5 production component recommendations; not the third-party VM’s capacity or HA guarantee. Source: https://docs.pingcap.com/tidb/stable/hardware-and-software-requirements/ (reviewed 2026-11-18). Supporting source: Different single-VM baseline — https://www.techlatest.net/support/tidb_support/aws_gettingstartedguide/index.html.

- License pricing: Documented. TiDB Community is Apache 2.0 licensed. PingCAP support and TiDB Cloud are separate commercial purchases. Review the licences of optional monitoring tools and other bundled components. The alternative Techlatest AMI bills USD 0.13/hour for seller support on its reviewed t2.large option, with AWS resources separate. Scope: TiDB Community self-managed software; Operator and third-party VM delivery have separate packaging/operating scope. Source: https://github.com/pingcap/tidb/blob/master/LICENSE (reviewed 2026-11-18). Supporting source: Separately transacted seller bundle pricing — https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4.

- Operating cost estimate: Sources checked — unresolved. Define SQL QPS, transaction mix, concurrency, indexes, TiKV replication, usable versus raw 1 TB, compaction headroom, TiFlash/TiCDC needs, monitoring and recovery targets. Price EKS and stateful nodes/storage across failure domains after benchmarking; the user count alone does not size this distributed database. The seller’s single-VM bundle does not provide the requested HA architecture. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://docs.pingcap.com/tidb/stable/hardware-and-software-requirements/ (reviewed 2026-11-18). Supporting source: Current AWS Linux EC2 rates; workload/topology still required — https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/. Supporting source: Single-VM price/topology is a different cost scope — https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4.

- Release snapshot / cadence: Documented. TiDB v8.5.8 was published August 27, 2026 and is the reviewed v8.5 LTS snapshot. Its notes include PD endpoint and TiKV dependency security fixes. The later v7.5.8 publication belongs to an older branch. Match Operator, TiKV, PD and optional component versions rather than treating the chart version as the database version. Techlatest’s AMI package 1.0.2 does not disclose its embedded database versions, so this upstream snapshot must not be inherited by that VM. Scope: Upstream TiDB v8.5 LTS snapshot; not a confirmed version for the third-party AWS image. Source: https://github.com/pingcap/tidb/releases/tag/v8.5.8 (reviewed 2026-11-18). Supporting source: Component fixes in v8.5.8 — https://docs.pingcap.com/tidb/stable/release-8.5.8. Supporting source: Separate seller package/version boundary — https://aws.amazon.com/marketplace/pp/prodview-ddl3tqewcoko4.




### Security and lifecycle reviews

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

- TiDB v8.5.8 PD endpoint and component security review (security-advisory): The release fixes potential SSRF/upstream response exposure in PD metric endpoints, GlobalConfig namespace access and dependency vulnerabilities in TiKV/DM. Scope: The v8.5.8 component release notes; a complete affected-version range and a universal exposure claim are not established. Conditions: Exposure depends on component versions, PD endpoint accessibility and configured dependencies. Community, Cloud and unrelated LTS branches must not be treated as identical deployments. Action: Review the fixed PD/TiKV/optional component versions, restrict management endpoints and follow the matching LTS upgrade procedure. Source: https://docs.pingcap.com/tidb/stable/release-8.5.8; reviewed 2026-11-18.




## Weaviate Self-Hosted

Self-hosted vector-search database for retrieval and AI applications.

- Listing: https://launchinyourcloud.com/directory/weaviate/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: BSD-3-Clause core outside the wl directory; wl code and associated enterprise features require a separate enterprise license/key.
- Licensing model: open-source
- Installation: Docker or Docker Compose, or a Kubernetes deployment using Helm. Google’s GKE guide uses Terraform to provision the cluster.
- Architecture: Customer-operated vector database, persistent storage and optional model integrations
- Operations: Customer manages authentication, storage, backup, scaling, configuration and upgrades.
- Product website: https://weaviate.io/
- Source review: 2026-11-21; cloud review: 2026-11-21; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The Docker defaults include anonymous access and default telemetry; production installations must configure the intended controls. Pre-vectorized data can be searched without an external vectorizer, but enabled embedding, reranking or generation integrations may call external providers. Telemetry is enabled by default and has a documented opt-out; the entire current codebase must not be described as uniformly BSD-licensed. Weaviate v1.39.17 fixes a v1.39 runtime-reindex restart bug in which writes arriving before reindex resumed could be absent from the new property index, or an incomplete index could be swapped in after partial files disappeared. Operators remaining on v1.39 should update and verify filter/search results; the primary reviewed release remains the newer v1.40.5 line.

The current repository distinguishes BSD-3-Clause code outside wl/ from enterprise-licensed wl/ code and features enabled by a license key. The complete current product is therefore classified as open-core, not uniformly BSD licensed.

Docker/Compose or Kubernetes runs a provisioned persistent database service. Data-plane ownership does not include optional external model integrations; choose and size those separately.


### Category fit

- databases-vector: Vector database supporting pre-vectorized search and configurable model integrations. Connected embedding/generation modules and enterprise features are separate dependencies.

- ai-tools: Self-hosted vector-search database for retrieval and AI applications.

### Deployment boundaries


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

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloud.google.com/kubernetes-engine/docs/tutorials/deploy-weaviate (checked 2026-11-21). 


### Cloud deployment evidence

- Weaviate self-managed AWS deployment options (aws): https://docs.weaviate.io/deploy/production/aws
  The vendor documents a self-managed EKS deployment path. Use that path for this listing: the same page also describes Shared Cloud marketplace SaaS, which is a separate deployment option.
  Source type: vendor-documentation; reviewed: 2026-11-21; vendor support: not-assessed.

- Deploy self-hosted Weaviate on Google Kubernetes Engine (gcp): https://docs.cloud.google.com/kubernetes-engine/docs/tutorials/deploy-weaviate
  Google documents provisioning a private GKE Standard or Autopilot cluster in the customer’s project with Terraform and installing Weaviate with Helm. The customer operates the database.
  Source type: provider-guide; reviewed: 2026-11-21; vendor support: not-assessed.


### Sources

- Docker and persistent-storage deployment: https://docs.weaviate.io/deploy/installation-guides/docker-installation

- Default telemetry and configuration: https://docs.weaviate.io/deploy/configuration/telemetry

- Core and enterprise license split: https://github.com/weaviate/weaviate/blob/main/LICENSE

- Weaviate v1.39.17 maintenance release: https://github.com/weaviate/weaviate/releases/tag/v1.39.17

- Runtime reindex restart fix: https://github.com/weaviate/weaviate/pull/13755

- Deploy self-hosted Weaviate on Google Kubernetes Engine: https://docs.cloud.google.com/kubernetes-engine/docs/tutorials/deploy-weaviate

### Licensing sources

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

### Infrastructure sources

- https://docs.weaviate.io/deploy/installation-guides/docker-installation


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Self-hosted Weaviate supports OpenID Connect alongside API keys, with Docker and Kubernetes configuration examples. Authentication and RBAC authorization are separate; configure issuer/client settings and role mapping, and disable anonymous access for production. Scope: Self-hosted database OIDC authentication. Source: https://docs.weaviate.io/deploy/configuration/authentication (reviewed 2026-11-20).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Documented. The self-managed authentication guide supports API keys and OIDC and also permits anonymous access. Configure authentication and authorization together; an anonymous quickstart is not a protected production endpoint. Scope: Weaviate database/API controls; not a vendor compliance attestation. Source: https://docs.weaviate.io/deploy/configuration/authentication (reviewed 2026-11-14).

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Docker guide supplies an official image and configurable Compose recipe. Its default example enables anonymous access; configure authentication, persistent volumes and required modules before exposing the service. Scope: Upstream self-hosted deployment; not a provider support or production-readiness certification. Source: https://docs.weaviate.io/deploy/installation-guides/docker-installation (reviewed 2026-11-14).

- Minimum footprint / sizing: Documented. The resource-planning guide estimates roughly 3 GB memory for one million uncompressed 384-dimensional float32 vectors using its two-times rule. HNSW connectivity, compression, payloads, replicas and concurrency change requirements; CPU affects query/import throughput. This is an index-sizing example, not a complete minimum or 1-TB/HA guarantee. Scope: Upstream vector-index memory example; full workload/topology sizing additional. Source: https://docs.weaviate.io/weaviate/concepts/resources (reviewed 2026-11-20).

- License pricing: Documented. Code outside the wl directory is BSD-3-Clause; wl contains separately licensed Enterprise functionality enabled by a licence key. The core licence does not grant those features. Obtain Enterprise pricing and support terms separately from infrastructure. Scope: Upstream core licence; commercial features, support and hosting priced separately. Source: https://raw.githubusercontent.com/weaviate/weaviate/main/LICENSE (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v1.40.5, published 2026-11-10. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. The maintained v1.39 branch has a separate v1.39.17 runtime-reindex restart fix; this does not replace the newer v1.40.5 primary snapshot. Scope: Upstream weaviate/weaviate release record; commercial editions and deployment packages may differ. Source: https://github.com/weaviate/weaviate/releases/tag/v1.40.5 (reviewed 2026-11-19). Supporting source: v1.39.17 maintenance release — https://github.com/weaviate/weaviate/releases/tag/v1.39.17. Supporting source: Runtime reindex fix — https://github.com/weaviate/weaviate/pull/13755.







## YugabyteDB Anywhere

Commercial self-managed database-as-a-service control plane for YugabyteDB clusters.

- Listing: https://launchinyourcloud.com/directory/yugabytedb-anywhere/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, oci
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial installed-software license; YugabyteDB core components have separate source licenses.
- Licensing model: commercial-only
- Installation: Installer or Helm deployment, followed by customer-cloud provider configuration
- Architecture: Customer-operated management control plane and distributed database universe nodes
- Operations: Customer operates YugabyteDB Anywhere and its database nodes while the software automates provisioning, scaling, backups and upgrades.
- Product website: https://www.yugabyte.com/yugabytedb-anywhere/
- Source review: 2026-11-14; cloud review: 2026-11-14; licensing review: 2026-11-14; infrastructure review: 2026-11-14

### Scope and qualifications

This entry covers YugabyteDB Anywhere, not the managed YugabyteDB Aeon service or a manual deployment of only the open-source database. Cloud provider configurations require customer credentials, network access and supported machine images.

YugabyteDB Anywhere is commercial installed software. The open-source YugabyteDB database and evaluation packages have separate terms and do not replace the production YBA entitlement.

YugabyteDB Anywhere and the database universe run as persistent control-plane and database-server workloads on VMs or Kubernetes.


### Category fit

- databases-vector: Provides a self-managed control plane for deploying and operating distributed YugabyteDB database clusters across customer cloud infrastructure.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/aws/ (checked 2026-11-14). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/azure/ (checked 2026-11-14). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/gcp/ (checked 2026-11-14). 

- oci: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/oci/ (checked 2026-11-14). 


### Cloud deployment evidence

- YugabyteDB Anywhere AWS provider (aws): https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/aws/
  Yugabyte documents customer AWS credentials, regions, networks and VM provisioning for YBA-managed database universes.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- YugabyteDB Anywhere Azure provider (azure): https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/azure/
  Yugabyte documents customer Azure subscription credentials, resource groups, networks and VM provisioning for YBA-managed universes.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- YugabyteDB Anywhere Google Cloud provider (gcp): https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/gcp/
  Yugabyte documents customer GCP service accounts, projects, regions and instance provisioning for YBA-managed universes.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.

- YugabyteDB Anywhere OCI provider (oci): https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/oci/
  Yugabyte documents customer OCI credentials, regions, availability domains and VM provisioning for YBA-managed universes.
  Source type: vendor-documentation; reviewed: 2026-11-14; vendor support: not-assessed.


### Sources

- YugabyteDB Anywhere overview: https://docs.yugabyte.com/stable/yugabyte-platform/

- Provider configurations: https://docs.yugabyte.com/stable/yugabyte-platform/configure-yugabyte-platform/

- Deployment planning: https://docs.yugabyte.com/stable/yugabyte-platform/create-deployments/create-universes-overview/

- Installed software license terms: https://www.yugabyte.com/legal/installed-software-terms/

### Licensing sources

- https://www.yugabyte.com/legal/installed-software-terms/

- https://docs.yugabyte.com/stable/faq/general/

### Infrastructure sources

- https://docs.yugabyte.com/stable/yugabyte-platform/

- https://docs.yugabyte.com/stable/yugabyte-platform/prepare/


### Buyer diligence


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

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


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. YugabyteDB Anywhere documents OIDC authentication for its management console with IdP/client configuration and user/role mapping. This is management-platform SSO, distinct from database-user OIDC and from the vendor-operated Aeon service. Scope: YugabyteDB Anywhere administrator console; database identities separate. Source: https://docs.yugabyte.com/stable/yugabyte-platform/administer-yugabyte-platform/oidc-authentication/ (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Documented. YBA documents manual database-release upload for air-gapped instances and additional software prerequisites for offline database nodes. Prepare dependencies and the management/data-plane network; this is not the default connected installation. Scope: Documented YBA offline release-management path. Source: https://docs.yugabyte.com/stable/yugabyte-platform/manage-deployments/ybdb-releases/ (reviewed 2026-11-14). Supporting source: Offline database-node prerequisites — https://docs.yugabyte.com/stable/yugabyte-platform/prepare/server-nodes-software/.

- Deployment artifact / IaC: Documented. The vendor YBA Installer deploys and manages YugabyteDB Anywhere using a downloaded release, YAML configuration and installer lifecycle commands. Provision the management host and permissions separately from database universe nodes; pin a supported release and configure storage, TLS and backups. Scope: YugabyteDB Anywhere management-platform installer, not the whole managed database estate. Source: https://docs.yugabyte.com/stable/yugabyte-platform/install-yugabyte-platform/install-software/installer/ (reviewed 2026-11-21). Deployment artifact: https://docs.yugabyte.com/stable/yugabyte-platform/install-yugabyte-platform/install-software/installer/. Artifact reference: Current stable vendor YBA Installer documentation.

- Minimum footprint / sizing: Documented. The YBA management-server VM requires 4 cores, 8 GB RAM and 215 GB disk on x86 Linux. Database universes run on separate nodes and need separate sizing; these figures are not a complete database footprint. Scope: YugabyteDB Anywhere management VM only; a license file is required. Source: https://docs.yugabyte.com/stable/yugabyte-platform/prepare/server-yba/ (reviewed 2026-11-14).

- License pricing: Documented. The installed-software terms explicitly include YugabyteDB Anywhere and license executable use under an Order Form with capacity metrics such as vCPU/CPU cores. Monitor contracted usage and review support, increases and renewal terms; the open-source database core licence is a different entitlement. Scope: April 2026 installed-software commercial terms for YugabyteDB Anywhere. Source: https://www.yugabyte.com/legal/installed-software-terms/ (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






