Postgres + pgvector hosting

Vector search inside the database you already trust.

Vector & dataPostgreSQL Licensefrom $5.99/mo
In short

Postgres + pgvector hosting at AIHostBox means a dedicated, single-tenant Postgres + pgvector instance on our infrastructure: we install it, pin it to a reviewed release, put it behind TLS on your domain, back it up nightly and keep it patched. Plans start at $5.99 per month and the admin account, the data and any API keys are yours.

One databaseSQL joinsHNSW & IVFFlatStandard backups

pgvector is a PostgreSQL extension, created and maintained by Andrew Kane, that adds a vector type and similarity search to the database you may already run. It stores vectors of up to 16,000 dimensions, builds HNSW and IVFFlat indexes, and provides L2, inner product, cosine, L1, Hamming and Jaccard distance operators. Half-precision, binary and sparse vector types cut storage for large embeddings, and since version 0.8 iterative index scans stop filtered queries from returning too few rows.

The case for it is that it is still Postgres: transactions, foreign keys, row-level security, full-text search and ordinary pg_dump backups all apply to your embeddings. That is also why it belongs on a server. Your application, a RAG framework or several services connect to it over the network at all hours, and HNSW indexes are searched fastest when they sit in memory, so the database wants RAM of its own rather than a laptop shared with a browser.

Postgres + pgvector hosting plans

StarterPersonal use & small teams
2 GB RAM · 1 vCPU · NVMe
$5.99/mo
Order
PlusBusy workflows & communities
4 GB RAM · 2 vCPU · NVMe
$9.99/mo
Order
ProHeavy pipelines & many users
8 GB RAM · 3 vCPU · NVMe
$16.99/mo
Order

Every plan is a dedicated single-tenant instance with NVMe storage, nightly off-box backups, TLS and managed patching. Quarterly, semi-annual and annual terms are discounted at checkout. Model tokens are not included — you bring your own key.

How we run Postgres + pgvector

A single PostgreSQL server from the official pgvector/pgvector image, with the vector extension enabled, data on NVMe and remote connections on port 5432 over TLS only.

What we configure for you

  • CREATE EXTENSION vector in your database, with your application role and password
  • shared_buffers and effective_cache_size sized to the plan’s RAM
  • maintenance_work_mem raised so HNSW index builds fit in memory
  • TLS required for remote connections, with SCRAM password authentication in pg_hba.conf
  • Nightly off-box backup of the database, and a pg_dump on request for your own copy

Which plan fits

Starter (2 GB, 1 vCPU) suits a prototype or up to roughly 150,000 768-dimension vectors. Plus (4 GB, 2 vCPU) handles a few hundred thousand 1,536-dimension vectors with the HNSW index in memory. Pro (8 GB, 3 vCPU) is for around a million 768-dimension vectors or heavy concurrent querying; storing them as halfvec roughly halves the memory needed.

The honest limits

Approximate indexes trade recall for speed, so ef_search and list counts need tuning against your data; well beyond a few million vectors on one node, a dedicated engine such as Qdrant or Milvus usually scales more comfortably.

What people run Postgres + pgvector for

Avoid a second store

Keep vectors beside your relational data.

Filtered similarity

A WHERE clause and a similarity ordering in the same query.

RAG store for a framework

Dify, Flowise, LangChain and LlamaIndex all ship a pgvector store you can point at this database.

Hybrid search

Combine Postgres full-text ranking with vector similarity for better retrieval.

Licence and version policy

ItemPosition
Upstream licencePostgreSQL License
Sold as managed hostingYes
TenancySingle tenant — one customer per instance
PatchingCritical advisories within 24 hours, high severity within 72

Our full position on licences, including the applications we decline to sell, is on the licensing page.

Reading on Postgres + pgvector

Works well with Postgres + pgvector

More Vector & data we host

Questions

Postgres + pgvector hosting: your questions

Which pgvector and Postgres versions do you run?
Current PostgreSQL with the current pgvector 0.8 release, from the official pgvector/pgvector images. Moving an existing database to a newer extension version is ALTER EXTENSION vector UPDATE, which we run for you; major Postgres upgrades are scheduled with you, because they need a dump and restore or pg_upgrade.
How many dimensions can I index?
The vector type stores up to 16,000 dimensions, but HNSW and IVFFlat indexes cover up to 2,000. For larger embeddings, such as 3,072-dimension models, index a halfvec expression (up to 4,000 dimensions) or ask the model for fewer dimensions if it supports that. Binary quantisation with the bit type is another route for very large sets.
HNSW or IVFFlat: which index should I use?
HNSW gives a better speed-to-recall trade-off and needs no training step, so it can be created on an empty table. IVFFlat builds faster and uses less memory, but should be created after the table holds data, because its lists come from existing rows. HNSW defaults are m=16 and ef_construction=64, with hnsw.ef_search=40 at query time.
Can I connect with psql and my usual drivers?
Yes. You get a connection string on port 5432 with TLS, plus a database and role for your application. Any Postgres driver works, and pgvector’s client libraries for Python, Node, Go, Ruby and other languages add vector type support on top of the drivers you already use.
How do I import existing embeddings?
Restore a pg_dump from another Postgres with pgvector, or bulk-load with COPY, which pgvector’s docs recommend over row-by-row inserts. Build the HNSW index after the load with maintenance_work_mem raised so the graph fits in memory; that is far quicker than indexing as rows arrive.

Run Postgres + pgvector without running a server

A dedicated Postgres + pgvector instance, deployed and maintained by us. Month to month, cancel whenever.