Databases · head to head
Convex vs Milvus

Convex
Databases
Reactive backend combining a document database, TypeScript server functions and live queries, source-available under the Functional Source Licence.
- From
- Free
- Free plan
- Yes

Milvus
Machine Learning
Open-source vector database for scalable similarity search
- From
- Free
- Free plan
- Yes
The short version
- Milvus is an open-source vector database.
- Milvus is free; Convex starts at $25/mo.
- Only Convex lists reactive queries; only Milvus lists billion-scale vectors.
- Where Milvus falls short: vector dimensions are capped at 32,768.
- Prices and features on this page were last checked on 13 November 2026.
Where they differ
Only the attributes on which Convex and Milvus actually diverge.
Identical on both: starting price (Free), free tier (Yes).
Not yet recorded: founded for Convex.
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 Convex
- Reactive queries
- TypeScript server functions
- ACID transactions
- Document database
- Scheduling and workflows
- File storage
- Text and vector search
- End-to-end types
Only in Milvus
- Billion-scale vectors
- Multiple index types
- GPU acceleration
- Hybrid search
- Data partitioning
- PyTorch
- TensorFlow
- Hugging Face
What people use each for
The jobs each tool is most often brought in to do.
Convex
- Collaborative applications where several users see the same data and every client must reflect a change immediatelynot Milvus
- Agent backends that need durable state, scheduled work and transactional writes without assembling a queue, a database and a cachenot Milvus
- Small product teams who need a complete backend, including auth integration, file storage and subscriptions, without hiring infrastructure engineersnot Milvus
- Prototypes that must become production without a rewrite of the data layer, where end-to-end TypeScript types remove a class of integration bugsnot Milvus
Milvus
- Self hosting a vector database for semantic searchnot Convex
- Storing and querying embeddings for retrieval augmented generationnot Convex
- Similarity search over images, audio or text at scalenot Convex
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Convex
- The Functional Source Licence is not an OSI open source licence: competing use is prohibited until each release reaches its second anniversary and converts to Apache 2.0, so you may self-host but you may not build a service on it
- Transactions are bounded at one second of user code, 16 MiB read and written, 32,000 documents scanned and 16,000 written, so every backfill, migration or bulk import has to be chunked into scheduled batches rather than written as a single operation
- There is no SQL and no query planner; you declare up to 32 indexes per table and traverse them, and joins are loops in TypeScript, so an unanticipated access pattern requires a schema and index change rather than a new query
- It is not an analytical database, so reporting means streaming data out to a warehouse and BI tools cannot be pointed at Convex directly, which adds a pipeline the architecture diagram did not originally include
- The application is written against Convex's function and client APIs rather than a standard protocol, so leaving means rewriting the data access layer and replacing the reactivity model, not repointing a connection string
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
Pricing, plan by plan
Convex
Free- Free & StarterFree
- Supports 1-6 developers
- Reactive database
- File storage
- Professional$25
- Supports up to 20 developers
- All Starter features
- Log streaming
- Business & Enterprise$2,500/month minimum
- Supports 50+ developers
- SAML/SSO
- Service SLAs
Milvus
Free- Open SourceFree
- Full features
- Self-hosted
- Community support
- Zilliz CloudFree
- Managed service
- Free tier available
Which should you pick?
Choose Convex if
- You need reactive queries.
- You want to start without paying.
- You also want typescript server functions.
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.
Questions people ask
- Is Convex or Milvus better?
- Neither clearly leads. Convex starts at Free and Milvus at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Convex or Milvus?
- Convex starts at Free and Milvus at Free.
- Does Convex or Milvus run on more platforms?
- Convex runs on Web. Milvus runs on Linux, macOS, Windows, Web.
- Can I use Convex for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Convex best used for?
- Convex is most often used for collaborative applications where several users see the same data and every client must reflect a change immediately, agent backends that need durable state, scheduled work and transactional writes without assembling a queue, a database and a cache, small product teams who need a complete backend, including auth integration, file storage and subscriptions, without hiring infrastructure engineers, prototypes that must become production without a rewrite of the data layer, where end-to-end typescript types remove a class of integration bugs. Of those, collaborative applications where several users see the same data and every client must reflect a change immediately and agent backends that need durable state, scheduled work and transactional writes without assembling a queue, a database and a cache are not what Milvus is typically brought in for.
- What can Convex do that Milvus cannot?
- Convex covers Reactive queries, TypeScript server functions, ACID transactions, Document database. Milvus covers Billion-scale vectors, Multiple index types, GPU acceleration, Hybrid search.
Answered from the vendors’ own pages
Convex: Is Convex open source?
It is source-available under FSL-1.1-Apache-2.0. You may read, modify and self-host it, but competing use is prohibited until each release converts to Apache 2.0 on its second anniversary.
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.
SourceConvex: Can I self-host it?
Yes. The backend, dashboard and CLI can run on your own infrastructure, with most of the features of the cloud product. Self-hosted instances include a telemetry beacon that can be disabled.
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.
SourceConvex: Does it support SQL?
No. Data is accessed through a TypeScript query builder over declared indexes. Relationships are traversed in code, which is explicit and type-safe but means no ad hoc querying.
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.
SourceConvex: What happens if a mutation exceeds the limits?
It fails rather than running longer, so bulk work must be split into batches and scheduled. The limits are per transaction: one second of user code, 16 MiB read and written, 32,000 documents scanned and 16,000 written.
Convex: How does reactivity actually work?
Queries are deterministic functions and Convex records the data each one read. When a mutation changes that data, affected queries are re-run and subscribed clients receive the new result, so cache invalidation is handled by the platform.
Related pages
Other head to heads
- Convex vs Readyset
- Convex vs DynamoDB
- Convex vs FaunaDB
- Convex vs LanceDB
- Convex vs Xata
- Convex vs Materialize
- Convex vs BigQuery
- Convex vs dbt
- Convex vs OpenSearch
- Convex vs TiDB
- Convex vs Tinybird
- Convex vs Canary Labs
- Convex vs Aiven
- Convex vs CosmosDB
- Convex vs DataStax
- Convex vs EMQX
- Convex vs Firebase Realtime Database
- Convex vs Firestore
- Convex vs Azure Machine Learning
- Convex vs Pinecone
- Convex vs Weaviate
- Convex vs Ray
- Convex vs Fal AI
- Convex vs Google Vertex AI
- Convex vs AWS SageMaker
- Convex vs Jupyter
- Convex vs Keras
- Convex vs LangChain
- Convex vs H2O.ai
- Convex vs Alteryx
- Convex vs Anaconda
- Convex vs Domino Data Lab
- Convex vs DVC
- Convex vs Hugging Face
- Convex vs Kubeflow
- Convex vs Semantic Kernel
- Milvus vs Readyset
- Milvus vs DynamoDB
- Milvus vs FaunaDB
- Milvus vs LanceDB
- Milvus vs Xata
- Milvus vs Materialize
- Milvus vs BigQuery
- Milvus vs dbt
- Milvus vs OpenSearch
- Milvus vs TiDB
- Milvus vs Tinybird
- Milvus vs Canary Labs
- Milvus vs Aiven
- Milvus vs CosmosDB
- Milvus vs DataStax
- Milvus vs EMQX
- Milvus vs Firebase Realtime Database
- Milvus vs Firestore
- Milvus vs Azure Machine Learning
- Milvus vs Pinecone
- Milvus vs Weaviate
- Milvus vs Ray
- Milvus vs Fal AI
- Milvus vs Google Vertex AI
- Milvus vs AWS SageMaker
- Milvus vs Jupyter
- Milvus vs Keras
- Milvus vs LangChain
- Milvus vs H2O.ai
- Milvus vs Alteryx
- Milvus vs Anaconda
- Milvus vs Domino Data Lab
- Milvus vs DVC
- Milvus vs Hugging Face
- Milvus vs Kubeflow
- Milvus vs Semantic Kernel
