Softwr

Machine Learning · head to head

Milvus vs Vitess

Milvus logo

Milvus

Machine Learning

Open-source vector database for scalable similarity search

From
Free
Free plan
Yes
Vitess logo

Vitess

Databases

Scalable database clustering system for horizontal scaling of MySQL

From
Free
Free plan
Yes

The short version

  • Milvus is an open-source vector database.
  • Both are free.
  • Only Milvus lists billion-scale vectors; only Vitess lists horizontal Sharding.
  • Where Milvus falls short: vector dimensions are capped at 32,768.
  • Where Vitess falls short: VTGate scatter queries without sharding key incur significant performance penalties.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Milvus and Vitess actually diverge.

Attributes where Milvus and Vitess differ
AttributeMilvusVitess
PlatformsLinux, macOS, Windows, WebLinux, macOS, Self-hosted
CategoryMachine LearningDatabases
Founded20172010

Identical on both: starting price (Free), free tier (Yes).

Not yet recorded: pricing model for Vitess.

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Milvus

  • Billion-scale vectors
  • Multiple index types
  • GPU acceleration
  • Hybrid search
  • Data partitioning
  • PyTorch
  • TensorFlow
  • Hugging Face

Only in Vitess

  • Horizontal Sharding
  • Connection Pooling
  • Query Routing
  • Online Schema Changes
  • Shard Management
  • Replication Management
  • Automated Failover
  • MySQL

Both cover

  • Linux support

What people use each for

The jobs each tool is most often brought in to do.

Milvus

  • Self hosting a vector database for semantic searchnot Vitess
  • Storing and querying embeddings for retrieval augmented generationnot Vitess
  • Similarity search over images, audio or text at scalenot Vitess

Vitess

  • Transaction processingnot Milvus
  • Data storagenot Milvus
  • Application backendnot Milvus
  • Reportingnot Milvus
  • Data analyticsnot Milvus

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Milvus

  • Vector dimensions are capped at 32,768
  • A collection is limited to 64 fields, 1,024 partitions and 16 shards
  • Only 1 index is allowed per field
  • Search returns at most 16,384 vectors as top-k, and nq is capped at 16,384
  • Input and output per RPC is capped at 64 MB for insert, search and query
  • VARCHAR values are limited to 65,535 characters
  • Data loaded into query nodes cannot exceed 90% of available memory
  • An instance supports at most 65,536 collections

Vitess

  • VTGate scatter queries without sharding key incur significant performance penalties
  • Foreign key constraints not enforced across shards, requiring application-level integrity handling
  • Single primary per keyspace limits multi-region write capabilities
  • Distributed transactions without proper sharding key routing suffer performance degradation

Pricing, plan by plan

Milvus

Free
  • Open SourceFree
    • Full features
    • Self-hosted
    • Community support
  • Zilliz CloudFree
    • Managed service
    • Free tier available

Vitess

Free

No published plan breakdown. See the Vitess review.

Which should you pick?

Choose Milvus if

  • You need billion-scale vectors.
  • You want to start without paying.
  • You work on Linux, macOS, Windows, Web.
  • You also want multiple index types.

Choose Vitess if

  • You need horizontal sharding.
  • You want to start without paying.
  • You work on Linux, macOS, Self-hosted.
  • You also want connection pooling.

Questions people ask

Is Milvus or Vitess better?
Neither clearly leads. Milvus starts at Free and Vitess at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Milvus or Vitess?
Milvus starts at Free and Vitess at Free.
Does Milvus or Vitess run on more platforms?
Milvus runs on Linux, macOS, Windows, Web. Vitess runs on Linux, macOS, Self-hosted.
Can I use Milvus for free?
Both have a free tier, so you can try either at no cost before committing.
What is Milvus best used for?
Milvus is most often used for self hosting a vector database for semantic search, storing and querying embeddings for retrieval augmented generation, similarity search over images, audio or text at scale. Of those, self hosting a vector database for semantic search and storing and querying embeddings for retrieval augmented generation are not what Vitess is typically brought in for.
What can Milvus do that Vitess cannot?
Milvus covers Billion-scale vectors, Multiple index types, GPU acceleration, Hybrid search. Vitess covers Horizontal Sharding, Connection Pooling, Query Routing, Online Schema Changes. Both handle Linux support.

Answered from the vendors’ own pages

Milvus: How much does Milvus cost?

Milvus is open-source and free to use and modify. The self-hosted version has no licensing cost. Zilliz Cloud (the managed SaaS version) does not publish pricing on the website.

Source
Vitess: Is Vitess free to use?

Yes. Vitess is completely free and open source under the Apache 2.0 license. It is a graduated CNCF project with no licensing costs or pricing tiers.

Source
Milvus: Is there a free or open-source version of Milvus?

Yes, Milvus is fully open-source and available for free. Milvus Lite is a lightweight option for learning and prototyping that can be installed via pip.

Source
Vitess: What databases does Vitess support?

Vitess supports MySQL and MariaDB as backend databases. It acts as a middleware layer that adds sharding and orchestration capabilities on top of these databases.

Source
Milvus: Does Milvus offer a managed cloud service?

Yes, Zilliz Cloud is a fully managed Milvus cloud offering with serverless and dedicated cluster options. Pricing must be requested from the company as it is not listed on the public website.

Source
Vitess: Does Vitess require Kubernetes to run?

No. Vitess can run on Kubernetes using the Vitess Operator, but it can also be deployed on traditional infrastructure. Kubernetes integration is optional and provides additional automation benefits.

Source
Vitess: How does Vitess handle cross-shard transactions?

Vitess supports distributed transactions across shards, but they require queries to be routed through the sharding key. Transactions without a proper sharding key can result in slower performance.

Source
Vitess: Does Vitess enforce foreign key constraints?

Vitess does not enforce foreign key constraints across shards by default. Referential integrity must be managed at the application layer, though per-database support can be enabled with limitations.

Source
Share

Related pages

Other head to heads