VectorChord

Azure Artificial Intelligence (AI) 1 variation

VectorChord, the vchord vector search extension for PostgreSQL, preinstalled with pgvector and ready on first boot.

Base
Hardened build
minimal ports, security patches applied at build time
Access
Unique credentials
generated on first boot, readable only by root
Verified
Boots working
services pass a health gate before release
Support
24/7, 365 days
by email and live chat, 24 hour response SLA

Variations

This product is available in the build below. Open it for the operating system, cloud and version detail, or read its deployment guide.

ProductCloudOperating systemVersion
VectorChord vector search on PostgreSQL 18 on Ubuntu 24.04 LTS Azure Ubuntu 24.04 18 View · Guide

Overview

VectorChord adds the vchordrq vector index to PostgreSQL. It partitions embeddings into lists, compresses them with RaBitQ quantisation and reranks the closest candidates, so similarity search runs as an ordinary SQL query next to the rest of your data. It works on the pgvector vector type and distance operators, so existing pgvector tables and queries carry over, and pgvector's own HNSW and IVFFlat indexes remain available alongside it.

It suits teams building retrieval augmented generation, semantic search or recommendations who want their embeddings inside the PostgreSQL database they already run rather than in a separate vector service.

Why the cloudimg image

cloudimg ships PostgreSQL 18 with VectorChord preloaded and pgvector installed at pinned versions, with no database cluster baked into the image. Each virtual machine creates its own cluster, TLS certificate and passwords on first boot and writes them to a root only file, and the server listens on loopback only until you choose to expose it over TLS. VectorChord is distributed under its AGPL v3 licence election with the corresponding source shipped in the image. A built in benchmark compares a vchordrq index with a pgvector HNSW index on the same data on your own machine, and every deployment comes with a step by step guide and 24/7 support.

Common uses

  • Retrieval augmented generation over embeddings stored in PostgreSQL
  • Semantic and similarity search with SQL filters and joins
  • Moving an existing pgvector workload to faster building indexes