Milvus hosting
Vector search built for very large collections.
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.
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
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
| Item | Position |
|---|---|
| Upstream licence | Apache-2.0 |
| Sold as managed hosting | Yes |
| Tenancy | Single tenant — one customer per instance |
| Patching | Critical 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
Milvus hosting: your questions
How do clients authenticate?
Which index types are available on CPU?
How do I back up and migrate collections?
Is there a web interface?
When is Milvus the wrong choice?
Run Milvus without running a server
A dedicated Milvus instance, deployed and maintained by us. Month to month, cancel whenever.