Databases & vector on Google Cloud

Application and analytical databases, vector search and retrieval.

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

ListingDocumented cloudsDeployment and infrastructureLicensingInstallationOperations and limitations
ClickHouse BYOCAWS, Azure, Google CloudVendor-operated BYOC
Servers / containers
Commercial Only

Commercial

Vendor-assisted BYOC onboardingClickHouse operates the BYOC service; the customer owns the cloud environment.
Scope and evidence

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.

  • ClickHouse BYOC customer account support — 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.

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

Cloud evidence reviewed 2026-11-12

CockroachDB BYOCAWS, Azure, Google CloudVendor-operated BYOC
Servers / containers
Commercial Only

Commercial CockroachDB BYOC service.

Vendor-assisted BYOC onboarding using scoped cross-account cloud identityCockroach Labs manages database provisioning, upgrades, backups, monitoring and incidents; the customer owns the cloud account, network and billing boundary.
Scope and evidence

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.

  • CockroachDB BYOC customer-cloud support — 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.

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

Cloud evidence reviewed 2026-11-14

Couchbase Server Enterprise EditionAWS, Azure, Google CloudCustomer-operated
Servers / containers
Commercial Only

Commercial subscription for Couchbase Server Enterprise Edition; Community Edition is separately licensed.

Couchbase Kubernetes Operator by Helm or downloaded package, then CouchbaseCluster resources for Enterprise EditionCustomer manages Kubernetes, storage, networking, security, backups and upgrade policy; the Operator automates database lifecycle operations.
Scope and evidence

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.

  • Couchbase Server Enterprise on EKS, AKS and GKE — 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.

    Vendor / upstream documentation · Reviewed 2026-11-19 · Scope: Enterprise Edition · Version: Server 7.2 through 8.0 in the reviewed compatibility matrix. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-19

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

Commercial Elastic Cloud Enterprise license required after the trial.

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

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

  • Elastic Cloud Enterprise on public cloud hosts — Elastic's current ECE installation guide explicitly supports public-cloud hosts on AWS, Google Cloud and Microsoft Azure and installs ECE on customer-prepared virtual machines.

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

Cloud evidence reviewed 2026-11-15

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

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

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

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

  • Elastic Cloud on Kubernetes on EKS, AKS and GKE — Elastic documents ECK for managed Kubernetes services including Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine. The customer owns and operates the cluster and persistent storage.

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

Cloud evidence reviewed 2026-11-17

Meilisearch Community EditionAWS, Google Cloud, DigitalOceanCustomer-operated
Servers / containers
Open Source / Open Core

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.

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.Customer manages the VM, operating system, network rules, master key, TLS, persistent indexes, backups, monitoring, capacity and version upgrades.
Scope and evidence

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.

  • Meilisearch Community Edition on Amazon EC2 — 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.

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

  • Meilisearch Community Edition on Google Compute Engine — 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.

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

  • Meilisearch Community Edition on a DigitalOcean Droplet — 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.

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

Cloud evidence reviewed 2026-11-16

MilvusAWS, Azure, Google CloudCustomer-operated
Servers / containers
Open Source / Open Core

Apache License 2.0 for upstream Milvus.

Run the official standalone Docker or versioned Docker Compose deployment; distributed deployments have separate operational requirements.Customer manages persistent volumes, collections, indexes, access controls, capacity, backups and upgrades.
Scope and evidence

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.

  • Milvus deployment on Amazon EKS — Official instructions provision Amazon EKS and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.

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

  • Milvus deployment on Azure Kubernetes Service — Official instructions provision Azure Kubernetes Service and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.

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

  • Milvus deployment on Google Kubernetes Engine — Official instructions provision Google Kubernetes Engine and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.

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

Cloud evidence reviewed 2026-11-12

Neo4j Self-ManagedAWS, Azure, Google CloudCustomer-operated
Servers / containers
Open Source / Open Core

GPLv3 Community Edition; Enterprise Edition uses a commercial Neo4j license.

Official Helm charts on EKS, AKS or GKE; cloud marketplace and VM options also existCustomer manages compute, storage, networking, security, backups, monitoring, capacity and upgrades.
Scope and evidence

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 Helm deployments on EKS, AKS and GKE — 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.

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

Cloud evidence reviewed 2026-11-14

Qdrant Self-HostedGoogle CloudCustomer-operated
Servers / containers
Open Source / Open Core

Apache 2.0 for the upstream database; managed cloud offerings and support have separate commercial terms.

Official Docker image for local/server deployment; production storage, access controls and scaling require configuration.Customer manages persistence, backups, access controls, upgrades and any distributed-cluster operations.
Scope and evidence

The local quickstart is an installation starting point, not a secured production configuration. Applications can supply their own vectors or use separately configured embedding models. External embedding APIs and hosted inference can receive source data even when the database is self-hosted; local FastEmbed is a documented alternative. This entry excludes Qdrant Cloud hosting. Qdrant 1.20.1, released November 13, 2026, prevents collection-scoped JWTs from viewing snapshot telemetry for collections they cannot access; operators using scoped JWTs should upgrade.

  • Self-operated Qdrant cluster on Google Kubernetes Engine — Google documents provisioning a regional GKE cluster and installing Qdrant with Helm and persistent disks. The customer operates the database cluster; this is separate from Qdrant Cloud and its separately offered Hybrid Cloud service.

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

Cloud evidence reviewed 2026-11-12

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

QuestDB Open Source is Apache License 2.0; QuestDB Enterprise is separately proprietary.

Vendor AWS OSS AMI 10.1.0, or customer VM binary/systemd/container installation; validate the AMI OS lifecycle; Azure Marketplace packaging is EnterpriseCustomer manages VM and OS, data disks, networking, authentication, backups, monitoring, upgrades and capacity.
Scope and evidence

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

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

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

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

  • QuestDB on Google Cloud — QuestDB documents deployment to customer Compute Engine with separate durable storage.

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

  • Vendor-published QuestDB Open Source AWS AMI — 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.

    Marketplace offer · Reviewed 2026-11-18 · Scope: QuestDB Open Source · Version: AMI package 10.1.0. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-18

Redis Software Self-ManagedAWS, Azure, Google CloudCustomer-operated
Servers / containers
Commercial Only

Commercial Redis Software subscription.

Redis operator on EKS, AKS or GKE; Linux, container and AWS AMI options are also availableCustomer manages cluster infrastructure, networking, persistence, backups, upgrades, monitoring and licensed capacity.
Scope and evidence

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.

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

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

Cloud evidence reviewed 2026-11-14

ScyllaDB Enterprise Self-ManagedAWS, Azure, Google Cloud, Oracle CloudCustomer-operated
Servers / containers
Source Available

ScyllaDB Source Available License Agreement for current Enterprise releases; eligibility and capacity limits apply unless covered by paid terms.

Official cloud image/AMI, with a documented AWS CloudFormation cluster exampleCustomer manages topology, networking, authentication, capacity, backups, monitoring, patching and upgrades.
Scope and evidence

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.

  • Self-managed ScyllaDB 2026.3 on AWS — Official instructions launch ScyllaDB AMIs into the customer's AWS VPC and distinguish this self-managed deployment from ScyllaDB Cloud.

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

  • Self-managed ScyllaDB 2026.3 on Google Cloud — Official instructions use the customer's active Google Cloud account and gcloud to launch ScyllaDB images and call the deployment self-managed.

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

  • Self-managed ScyllaDB 2026.3 on Azure — Official instructions use the customer's Azure subscription and resource group to create a ScyllaDB VM and call the deployment self-managed.

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

  • Self-managed ScyllaDB 2026.3 on OCI — 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.

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

Cloud evidence reviewed 2026-11-19

TiDB Community Self-HostedAWS, Google Cloud, Azure, Alibaba CloudCustomer-operated
Servers / containers
Open Source / Open Core

Apache License 2.0.

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 topologyCustomer manages the chosen Kubernetes cluster or VM, operating system/node pools, persistent storage, networking, database identities, backups, monitoring, upgrades, scaling and database operations.
Scope and evidence

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.

  • TiDB on Amazon EKS — PingCAP documents customer EKS node pools, storage and TiDB Operator deployment.

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

  • TiDB on Google Kubernetes Engine — PingCAP documents customer GKE node pools, persistent disks and TiDB Operator deployment.

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

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

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

  • TiDB on Alibaba Cloud ACK — 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.

    Vendor / upstream documentation · Reviewed 2026-11-18 · Version: TiDB Operator guide v1.4. Vendor support commitment: not assessed; confirm the selected release and contract.

  • Techlatest TiDB OSS single-VM bundle in customer EC2 — 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.

    Third party package · Reviewed 2026-11-18 · Scope: Repackaged open-source TiDB bundle · Version: Seller package 1.0.2; embedded database versions unreported. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-18

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

BSD-3-Clause core outside the wl directory; wl code and associated enterprise features require a separate enterprise license/key.

Docker or Docker Compose, or a Kubernetes deployment using Helm. Google’s GKE guide uses Terraform to provision the cluster.Customer manages authentication, storage, backup, scaling, configuration and upgrades.
Scope and evidence

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.

  • Weaviate self-managed AWS deployment options — 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.

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

  • Deploy self-hosted Weaviate on Google Kubernetes Engine — 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.

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

Cloud evidence reviewed 2026-11-21

YugabyteDB AnywhereAWS, Azure, Google Cloud, Oracle CloudCustomer-operated
Servers / containers
Commercial Only

Commercial installed-software license; YugabyteDB core components have separate source licenses.

Installer or Helm deployment, followed by customer-cloud provider configurationCustomer operates YugabyteDB Anywhere and its database nodes while the software automates provisioning, scaling, backups and upgrades.
Scope and evidence

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 AWS provider — Yugabyte documents customer AWS credentials, regions, networks and VM provisioning for YBA-managed database universes.

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

  • YugabyteDB Anywhere Azure provider — Yugabyte documents customer Azure subscription credentials, resource groups, networks and VM provisioning for YBA-managed universes.

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

  • YugabyteDB Anywhere Google Cloud provider — Yugabyte documents customer GCP service accounts, projects, regions and instance provisioning for YBA-managed universes.

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

  • YugabyteDB Anywhere OCI provider — Yugabyte documents customer OCI credentials, regions, availability domains and VM provisioning for YBA-managed universes.

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

Cloud evidence reviewed 2026-11-14

Deployment evidence and category fit

ClickHouse BYOC

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

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.

  • ClickHouse BYOC customer account support ↗

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

    The vendor explicitly offers its managed BYOC service in the customer AWS, Google Cloud or Azure account. This establishes provider compatibility for the commercial BYOC offering rather than a generic open-source Docker deployment; agree availability, access, region and operational boundaries with the vendor.

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

CockroachDB BYOC

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

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.

  • CockroachDB BYOC customer-cloud support ↗

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

    Cockroach Labs explicitly offers BYOC in the customer's AWS, Azure or Google Cloud account. The vendor operates database services using scoped cross-account identity while the customer retains the cloud account and data-plane boundary.

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

Couchbase Server Enterprise Edition

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

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.

  • Couchbase Server Enterprise on EKS, AKS and GKE ↗

    Vendor / upstream documentation · Reviewed 2026-11-19 · Scope: Enterprise Edition · Version: Server 7.2 through 8.0 in the reviewed compatibility matrix. Vendor support commitment: not assessed; confirm the selected release and contract.

    Couchbase states that the Operator deploys and manages Server Enterprise Edition and is certified for Amazon EKS, Microsoft AKS and Google GKE. Database pods, services and storage run in the customer's cluster; this is not Couchbase Capella.

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

Elastic Cloud Enterprise

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

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

  • Elastic Cloud Enterprise on public cloud hosts ↗

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

    Elastic's current ECE installation guide explicitly supports public-cloud hosts on AWS, Google Cloud and Microsoft Azure and installs ECE on customer-prepared virtual machines.

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

Elastic Cloud on Kubernetes

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

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

  • Elastic Cloud on Kubernetes on EKS, AKS and GKE ↗

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

    Elastic documents ECK for managed Kubernetes services including Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine. The customer owns and operates the cluster and persistent storage.

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

Meilisearch Community Edition

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

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.

  • Meilisearch Community Edition on Google Compute Engine ↗

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

    The vendor documents a production-oriented installation on a customer Google Compute Engine VM with billing enabled, including the official binary installer, dedicated service account, persistent data directory, systemd service and firewall configuration. The customer operates the VM and search service.

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

Milvus

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

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.

  • Milvus deployment on Google Kubernetes Engine ↗

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

    Official instructions provision Google Kubernetes Engine and deploy Milvus using Helm. Review persistent storage, object storage, networking and cluster sizing for the selected version.

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

Neo4j Self-Managed

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

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 Helm deployments on EKS, AKS and GKE ↗

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

    Neo4j's Operations Manual documents standalone and clustered Helm deployments on Amazon EKS, Microsoft AKS and Google GKE. Edition and license requirements differ between standalone Community and clustered Enterprise deployments.

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

Qdrant Self-Hosted

Vector database for similarity and hybrid retrieval in AI applications. Model inference and embedding creation are separate from the core database deployment.

The local quickstart is an installation starting point, not a secured production configuration. Applications can supply their own vectors or use separately configured embedding models. External embedding APIs and hosted inference can receive source data even when the database is self-hosted; local FastEmbed is a documented alternative. This entry excludes Qdrant Cloud hosting. Qdrant 1.20.1, released November 13, 2026, prevents collection-scoped JWTs from viewing snapshot telemetry for collections they cannot access; operators using scoped JWTs should upgrade.

  • Self-operated Qdrant cluster on Google Kubernetes Engine ↗

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

    Google documents provisioning a regional GKE cluster and installing Qdrant with Helm and persistent disks. The customer operates the database cluster; this is separate from Qdrant Cloud and its separately offered Hybrid Cloud service.

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

QuestDB Open Source Self-Hosted

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

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 on Google Cloud ↗

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

    QuestDB documents deployment to customer Compute Engine with separate durable storage.

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

Redis Software Self-Managed

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

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.

  • Redis Software on EKS, AKS and GKE ↗

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

    Redis lists and tests its current Kubernetes operator on Amazon EKS, Microsoft AKS and Google GKE. The customer operates the Kubernetes cluster and Redis Software deployment; Redis Cloud is separate.

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

ScyllaDB Enterprise Self-Managed

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

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.

  • Self-managed ScyllaDB 2026.3 on Google Cloud ↗

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

    Official instructions use the customer's active Google Cloud account and gcloud to launch ScyllaDB images and call the deployment self-managed.

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

TiDB Community Self-Hosted

Provides a distributed SQL database with horizontally scaled storage and query services.

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.

  • TiDB on Google Kubernetes Engine ↗

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

    PingCAP documents customer GKE node pools, persistent disks and TiDB Operator deployment.

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

Weaviate Self-Hosted

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

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.

  • Deploy self-hosted Weaviate on Google Kubernetes Engine ↗

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

    Google documents provisioning a private GKE Standard or Autopilot cluster in the customer’s project with Terraform and installing Weaviate with Helm. The customer operates the database.

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

YugabyteDB Anywhere

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

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 Google Cloud provider ↗

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

    Yugabyte documents customer GCP service accounts, projects, regions and instance provisioning for YBA-managed universes.

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

Deployment and procurement checks

Private offers
Cloud Marketplace vendors can negotiate a private offer for a specified Cloud Billing account. Check duration, renewal terms and commitment treatment in the actual agreement. Provider source ↗ · Reviewed 2026-11-14
Private connectivity
Private Service Connect connects VPC consumers to supported managed or producer services. Confirm the actual product endpoint and network/DNS architecture. Provider source ↗ · Reviewed 2026-11-14
External workload access
Workload Identity Federation can grant external workloads scoped Google Cloud access without long-lived service-account keys. Validate the trust configuration and exact roles. Provider source ↗ · Reviewed 2026-11-14
Regulated environments
Assured Workloads applies control packages for residency and access boundaries. Confirm supported services, regions and the product deployment; it is not automatic product certification. Provider source ↗ · Reviewed 2026-11-14

For every provider, confirm marketplace/private-offer terms, commitment eligibility, regional service availability, private connectivity and any vendor access against your selected deployment. Provider capabilities do not automatically establish application support.

Plan this deployment

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

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

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