Databases & vector

Application and analytical databases, vector search and retrieval.

19 listings, including 19 from other publishers. Entries cover the deployment options documented on their individual pages.

Watch this category with RSS · Build a requirements shortlist

Deployment comparison

ListingDocumented cloudsDeployment and infrastructureLicensingInstallationOperations and limitations
Apache Doris Self-HostedAWS, Alibaba Cloud, AzureCustomer-operated
Servers / containers
Open Source / Open Core

Apache License 2.0 for the core project; optional third-party components can carry separate or incompatible licenses.

Doris Operator on AWS EKS or Alibaba ACK/ACS, or cloudimg’s Azure VM image; pin application/operator/image versions separatelyCustomer 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.
Scope and evidence

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 on Amazon EKS — 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.

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

  • Apache Doris on Alibaba Cloud ACK/ACS — 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.

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

  • cloudimg Apache Doris VM in a customer Azure subscription — 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.

    Third party package · Reviewed 2026-11-18 · Version: Guide application 4.0.6; Azure image latest must be resolved. Vendor support commitment: not assessed; confirm the selected release and contract.

Cloud evidence reviewed 2026-11-18

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

OpenSearchRailwayCustomer-operated
Servers / containers
Open Source / Open Core

Apache License 2.0 for upstream OpenSearch. Separately operated managed services and connected model or data services have their own terms.

Run official Docker images and customize the documented Docker Compose examples; native package and tarball installations are also documented.Customer manages cluster sizing, storage, shard and replica layout, TLS, users and roles, ingestion, snapshots, monitoring and upgrades.
Scope and evidence

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

  • Self-operated OpenSearch and Dashboards on Railway — The community recipe deploys OpenSearch 3 and Dashboards as customer-project services, with the search API on private networking. Its wrappers derive from upstream OpenSearch images. Review node count, heap/storage sizing, security plugin configuration, TLS and backups; this is separate from Amazon OpenSearch Service and does not imply high availability.

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

Cloud evidence reviewed 2026-11-12

PostgreSQLAWS, AzureCustomer-operated
Servers / containers
Open Source / Open Core

PostgreSQL License, a permissive OSI-approved open-source license.

Install supported operating-system binary packages or build the official source distribution on customer-operated hosts.Customer manages database users, network access, storage, backups, replication, query tuning and supported-version updates.
Scope and evidence

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.

  • Self-managed PostgreSQL migration to Amazon EC2 — AWS documents rehosting PostgreSQL on EC2 with the customer retaining database operations. This is separate from Amazon RDS for PostgreSQL.

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

  • PostgreSQL on Azure VMs versus managed PostgreSQL — 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.

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

Cloud evidence reviewed 2026-11-12

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

Supabase Self-HostedAWS, Railway, VultrCustomer-operated
Servers / containers
Open Source / Open Core

Open-source components with individual licenses; the Supabase platform repository uses Apache-2.0

Official Docker Compose distribution, community AWS CloudFormation template, Railway project template, or Vultr Marketplace server imageCustomer manages provisioning, hardening, database maintenance, scaling, backups and monitoring; self-hosting is community-supported.
Scope and evidence

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.

  • Supabase community AWS CloudFormation/CDK deployment — 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.

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

  • Self-host Supabase in a Railway project — 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.

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

  • Deploy the Supabase Marketplace application on Vultr Compute — 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.

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

Cloud evidence reviewed 2026-11-21

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

Choose 2–4 listings to compare

Browse listing cards

How these listings fit

Apache Doris Self-Hosted
Runs a persistent distributed analytical database on customer-controlled compute and storage.
ClickHouse BYOC
Managed analytical database with its data plane in your cloud account.
CockroachDB BYOC
Provides a managed distributed SQL database whose data-plane resources run inside the customer's cloud account.
Couchbase Server Enterprise Edition
Distributed NoSQL database deployed and lifecycle-managed in customer-controlled Kubernetes clusters.
Elastic Cloud Enterprise
Operates Elasticsearch clusters that provide document, full-text and vector search in customer infrastructure.
Elastic Cloud on Kubernetes
Elasticsearch provides distributed document storage, full-text search and vector search in a customer cluster.
Meilisearch Community Edition
Application search engine with typo-tolerant full-text search and semantic or hybrid retrieval over vector embeddings.
Milvus
Vector database for approximate nearest-neighbor retrieval over embeddings and associated metadata.
Neo4j Self-Managed
Provides a graph database with Cypher queries, graph traversal and vector-index capabilities in customer-operated deployments.
OpenSearch
Indexes and searches vectors alongside metadata, with lexical, nearest-neighbor, semantic and hybrid retrieval. Embedding generation requires an appropriate configured model or externally generated vectors.
PostgreSQL
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.
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.
QuestDB Open Source Self-Hosted
Provides a high-performance time-series database with SQL and ingestion protocols on customer infrastructure.
Redis Software Self-Managed
Provides commercial in-memory data, search and vector capabilities in a customer-operated Redis Enterprise cluster.
ScyllaDB Enterprise Self-Managed
Distributed NoSQL wide-column database for high-throughput, low-latency application data.
Supabase Self-Hosted
A PostgreSQL-based application data platform with database APIs, authentication and storage services. This entry covers the self-hosted stack.
TiDB Community Self-Hosted
Provides a distributed SQL database with horizontally scaled storage and query services.
Weaviate Self-Hosted
Vector database supporting pre-vectorized search and configurable model integrations. Connected embedding/generation modules and enterprise features are separate dependencies.
YugabyteDB Anywhere
Provides a self-managed control plane for deploying and operating distributed YugabyteDB database clusters across customer cloud infrastructure.

Review dates and sources appear on each listing. Functionality, edition, deployment and licensing must be checked together. Filter this category with cloud and deployment controls →

All categories · Suggest a listing or correction