Milvus hosting

Vector search built for very large collections.

Vector & dataApache-2.0from $18.99/mo
In short

Milvus hosting at AIHostBox means a dedicated, single-tenant Milvus 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 $18.99 per month and the admin account, the data and any API keys are yours.

Billion-scaleMultiple index typesPartitionsAttu UI

Milvus is an open-source vector database created by Zilliz and hosted as a graduated project of the LF AI & Data Foundation. It is designed for very large collections, with a wide choice of index types, hybrid search across dense and sparse vectors, partitions, scalar filtering and built-in full-text search with BM25. Client SDKs exist for Python, Java, Go and Node.js, and most RAG frameworks ship a Milvus connector. Collections can be split into partitions and filtered on scalar fields before the vector comparison runs.

The standalone deployment is three services working together: Milvus itself, etcd for metadata and MinIO for segment storage. That is a real database with a durable storage layer, not an in-process library, and it needs memory to match: upstream asks for 8 GB for standalone. A dedicated server keeps the indexes loaded and the object store on disk you do not have to manage. You also get stable gRPC and REST endpoints that several applications can share at the same time.

Milvus hosting plans

ProRecommended minimum
8 GB RAM · 4 vCPU · NVMe
$18.99/mo
Order
MaxLarge document sets
12 GB RAM · 6 vCPU · NVMe
$27.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 Milvus

The official standalone docker-compose: milvus-standalone, etcd for metadata and MinIO for object storage, each on its own persistent volume, with gRPC on port 19530.

What we configure for you

  • common.security.authorizationEnabled set to true, default root password replaced
  • MinIO access keys generated per instance rather than the compose defaults
  • gRPC endpoint on 19530 over TLS on your hostname
  • Health and WebUI port 9091 kept private
  • etcd, MinIO and Milvus volumes included in the nightly off-box backup

Which plan fits

Pro (8 GB, 4 vCPU) matches upstream’s standalone minimum and suits around a million 768-dimension vectors under HNSW alongside the service overhead. Max (12 GB, 6 vCPU) leaves room for larger in-memory indexes or DiskANN on collections that no longer fit in RAM.

The honest limits

Milvus has a heavy baseline footprint before any data is loaded, and GPU indexes are not available on CPU plans. Distributed cluster mode is out of scope; we run standalone.

What people run Milvus for

Large corpora

When a lighter store stops fitting in memory.

Index experimentation

Compare IVF, HNSW and others on the same data.

Hybrid keyword and vector search

Combine BM25 full-text and dense vectors in one query for better RAG recall.

Licence and version policy

ItemPosition
Upstream licenceApache-2.0
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 Milvus

Works well with Milvus

More Vector & data we host

Questions

Milvus hosting: your questions

How do clients authenticate?
We enable common.security.authorizationEnabled, so every connection needs a user and password passed as a token. Milvus creates a root user on first start; we replace the default password and you can add further users and roles through the SDK or Attu.
Which index types are available on CPU?
The CPU indexes: FLAT, the IVF family (IVF_FLAT, IVF_SQ8, IVF_PQ), HNSW, SCANN and DiskANN, plus sparse inverted indexes for BM25 and sparse embeddings. GPU indexes such as GPU_CAGRA need NVIDIA hardware and are not available on our plans.
How do I back up and migrate collections?
Data lives in MinIO segments with metadata in etcd, and both volumes are covered by the nightly off-box backup. For moving collections between Milvus instances, the official milvus-backup tool exports and restores whole collections, which is also the cleanest way to migrate from a self-run install.
Is there a web interface?
Milvus has a built-in WebUI for inspecting the running node, and Attu, a separate open-source GUI from the Milvus project, for browsing collections, running searches and managing users. We can run Attu next to your instance on request.
When is Milvus the wrong choice?
For a few hundred thousand vectors or a single RAG app, Qdrant, Chroma or pgvector use less memory and have fewer moving parts. Milvus earns its footprint when collections grow into tens of millions of vectors or you need its range of index types.

Run Milvus without running a server

A dedicated Milvus instance, deployed and maintained by us. Month to month, cancel whenever.