vespa.html

Vespa

Yahoo-built distributed search + vector engine. Hybrid retrieval at extreme scale.

VISIT VESPA

Quick facts

  • CategorySelf-hosted
  • EngineJava / C++
  • PricingFreemium
  • LicenseApache-2.0
  • Created2017
  • GitHub stars6.4k
  • Hybrid searchNative
  • Edge-readyNo
  • Multi-tenantNative
  • Max dimensions65,535

What it is

Vespa is a distributed search + ranking + vector engine open-sourced by Yahoo in 2017. Used for the largest hybrid retrieval workloads on the public internet (Yahoo, Spotify, large e-commerce). Mature, capable, operationally heavy, smaller community than Milvus or Weaviate.

Best for

  • Hybrid retrieval at extreme scale (search + ranking + vector all in one engine)
  • Apps that need custom ranking expressions
  • Teams with serious search-engineering capacity

When not to pick it

Skip Vespa for greenfield projects — the learning curve is steep and the Java/C++ stack is heavy. Most teams should use Weaviate or Qdrant.

My take

Vespa is the right answer for one specific shape (hybrid retrieval at extreme scale with custom ranking). Outside that niche, simpler options win.

Links

Similar tools you should also consider

Milvus

Distributed vector DB built for billion-scale workloads. Heavy, capable, China-AI-aligned.

Read the take →

Weaviate

Open-source self-hostable vector database with hybrid search and module ecosystem.

Read the take →

If Vespa is your pick — the next conversation is short

The 30-min call is where your vector-DB choice becomes a real RAG architecture, a chunking + reranking strategy that actually works for your corpus, and a price range you can take to your stakeholders. Describe your data shape, your query patterns, your latency budget. I tell you whether Vespa is genuinely your fit.