Softwr

Developer Tools · head to head

Cortex vs Milvus

Cortex logo

Cortex

Developer Tools

Internal developer portal that scores service ownership and maturity rather than just cataloguing services

From
On request
Free plan
No
Milvus logo

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; Cortex prices on request.
  • Only Cortex lists service catalogue; 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 20 November 2026.

How do Cortex and Milvus differ?

Cortex and Milvus differ on starting price (On request against Free), pricing model (Quote against Freemium) and free tier (No against Yes). Only the attributes on which Cortex and Milvus actually diverge.

Attributes where Cortex and Milvus differ
AttributeCortexMilvus
Starting priceOn requestFree
Pricing modelQuoteFreemium
Free tierNoYes
PlatformsWeb, APILinux, macOS, Windows, Web
CategoryDeveloper ToolsMachine Learning

Not yet recorded: founded for Cortex.

Which features does each one have?

They share no listed features; 8 appear only for Cortex and 14 only for Milvus. 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 Cortex

  • Service catalogue
  • Scorecards
  • Initiatives
  • Self-service templates
  • Query language
  • Eng intelligence
  • Integrations layer
  • On-call and ownership mapping

Only in Milvus

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

What is each one used for?

Milvus is most often brought in for self hosting a vector database for semantic search. The jobs each tool is most often brought in to do.

Cortex

  • A platform team that needs to prove to leadership how far a Kubernetes or framework migration has actually progressed across hundreds of servicesnot Milvus
  • An organisation where ownership of production services is genuinely unknown after reorganisations or acquisitionsnot Milvus
  • Enforcing production readiness standards on new services at creation time rather than at incident reviewnot Milvus
  • Replacing a self-hosted Backstage that is consuming a full-time engineer or two just to stay upgradednot Milvus

Milvus

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

Where do Cortex and Milvus fall short?

Milvus's most cited limit: vector dimensions are capped at 32,768. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Cortex

  • Pricing is quote only, so a platform team cannot build a business case or compare against the true cost of self-hosted Backstage without entering a sales cycle first
  • The catalogue is only as accurate as the metadata you supply, so an organisation with inconsistent repository conventions spends its first quarter cleaning data before any scorecard means anything
  • Scorecards create political friction: publishing a per-team grade turns an engineering standard into a performance metric, and teams will game the rules rather than fix the underlying issue
  • It is closed source and hosted, so organisations with strict data residency or air-gap requirements have limited options compared with running Backstage themselves
  • Value scales with organisation size, so a company with fifty engineers and thirty services will find the catalogue tells them nothing they did not already know while still paying an enterprise contract

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

How much do Cortex and Milvus cost?

Cortex is priced on request; Milvus is free to use. Plan by plan below, from each vendor's own pricing page.

Cortex

On request
  • CortexOn request
    • Service catalogue and ownership mapping
    • Scorecards and initiatives
    • Self-service templates

Milvus

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

Which should you pick?

Choose Cortex if

  • You need service catalogue.
  • You work on Web, API.
  • You also want scorecards.

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 Cortex or Milvus better?
Neither clearly leads. Cortex starts at On request and Milvus at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cortex or Milvus?
Milvus has a free tier; the other does not. Paid plans start at On request for Cortex and Free for Milvus.
Does Cortex or Milvus run on more platforms?
Cortex runs on Web, API. Milvus runs on Linux, macOS, Windows, Web.
Can I use Milvus for free?
Yes. Milvus has a free tier, so you can try it without paying. Cortex starts at On request.
What is Cortex best used for?
Cortex is most often used for a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services, an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions, enforcing production readiness standards on new services at creation time rather than at incident review, replacing a self-hosted backstage that is consuming a full-time engineer or two just to stay upgraded. Of those, a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services and an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions are not what Milvus is typically brought in for.
What can Cortex do that Milvus cannot?
Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates. Milvus covers Billion-scale vectors, Multiple index types, GPU acceleration, Hybrid search.

Answered from the vendors’ own pages

Cortex: How is Cortex different from Backstage?

Backstage is an open source framework you build and staff. Cortex is a hosted product with scorecards and initiatives out of the box and no platform team required to keep it running.

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
Cortex: Is pricing published?

No. Cortex requires a sales conversation and prepares a custom proposal.

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
Cortex: Can it self-host?

It is offered as a hosted product; on-premise arrangements are handled through sales rather than published.

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
Cortex: What is the main adoption risk?

Bad or missing service metadata. The catalogue and every scorecard on top of it inherit whatever quality your repositories already have.

Share

Related pages

Other head to heads