← Back to home
Comparison · DevOps

GraphHopper vs Weaviate

A side-by-side editorial comparison of GraphHopper and Weaviate — release velocity, themes, recent moves, and the top alternatives to consider.

GraphHopper vs Weaviate: at a glance

FeatureGraphHopperWeaviate
SectorDevOpsDevOps
Velocity score0.08.8
Sparks · 30d03
Top themesrouting, openstreetmap, custom-models, navigationvector-search, agent-memory, quantization, disk-indexing
Last editorial update1mo ago10h ago
WebsiteVisit →Visit →

What is GraphHopper?

GraphHopper finished moving vehicle profiles into custom models, then went back to OSM tags.

GraphHopper ships a major roughly every six months, with 11.0 in October 2025 the most recent. The architectural work happened in 9.0, which moved vehicle encoded values into the custom model, removed the built-in vehicle parsers' name property and the wheelchair parsers, allowed external encoded values in custom models, and blocked built-in custom model filenames. 10.0 then spent itself on storage layout — byte-based edge storage, a Map-based KVStorage API, wider georef fields — and 11.0 is almost entirely OSM tag interpretation: maxspeed=none handling, separate foot and bike road access, cycleway oneway combinations, toll parsing moved into a country-aware parser.

Read the full GraphHopper trajectory →

What is Weaviate?

Weaviate ships Engram agent memory, HFresh disk indexing, and 4-bit quantization in quick succession

Weaviate 1.39 is the current stable release, having GA'd the Boost API and MMR diversity selection while introducing an experimental Search REST API. Two major storage advances landed in rapid succession: HFresh, a disk-based vector index that keeps vectors off the heap entirely, and 4-bit Rotational Quantization, which compresses stored vectors with minimal accuracy loss. Above the storage layer, Engram — a named agent memory product — is the most significant architectural addition: it lets builders configure extraction topics, scopes, and retrieval modes as first-class settings rather than building memory pipelines by hand.

Read the full Weaviate trajectory →

GraphHopper vs Weaviate: editorial side-by-side

G0.0

GraphHopper finished moving vehicle profiles into custom models, then went back to OSM tags.

◆ Current state

GraphHopper ships a major roughly every six months, with 11.0 in October 2025 the most recent. The architectural work happened in 9.0, which moved vehicle encoded values into the custom model, removed the built-in vehicle parsers' name property and the wheelchair parsers, allowed external encoded values in custom models, and blocked built-in custom model filenames. 10.0 then spent itself on storage layout — byte-based edge storage, a Map-based KVStorage API, wider georef fields — and 11.0 is almost entirely OSM tag interpretation: maxspeed=none handling, separate foot and bike road access, cycleway oneway combinations, toll parsing moved into a country-aware parser.

◆ Where it's heading

The configuration model is settled and the effort has moved to routing quality. Nearly every change in 11.0 is about reading OSM tags more faithfully for a specific mode — bicycle handling on living streets, foot instructions at junctions, MTB speeds on compacted surfaces, HGV tolls by country — which is the long tail of work that separates a routing engine that runs from one people trust. Turn restrictions are the recurring source of real bugs, appearing across 9.0, 10.0, 10.1 and 11.0 with via-way handling repeatedly needing correction. The new POST /navigate endpoint accepting a GraphHopper request is the one API-surface addition in this window.

◆ Prediction

Expect continued profile-level tuning driven by OSM tagging edge cases rather than architectural change, since three consecutive majors have narrowed in that direction. Turn restriction handling with multiple or overlapping via-ways is the most likely source of the next bugfix release, given its record across every version here.

W
Weaviate
DEVOPS
8.8

Weaviate ships Engram agent memory, HFresh disk indexing, and 4-bit quantization in quick succession

◆ Current state

Weaviate 1.39 is the current stable release, having GA'd the Boost API and MMR diversity selection while introducing an experimental Search REST API. Two major storage advances landed in rapid succession: HFresh, a disk-based vector index that keeps vectors off the heap entirely, and 4-bit Rotational Quantization, which compresses stored vectors with minimal accuracy loss. Above the storage layer, Engram — a named agent memory product — is the most significant architectural addition: it lets builders configure extraction topics, scopes, and retrieval modes as first-class settings rather than building memory pipelines by hand.

◆ Where it's heading

Weaviate is executing a two-layer expansion: at the bottom, making the vector store cheaper and more flexible (quantization, disk-based indexing, query profiling); at the top, building agent-native abstractions that make Weaviate more than a search backend (Engram memory, effort tiers, Search REST API). The direction has shifted from 'fast vector database' toward 'infrastructure for AI agent memory and retrieval systems.' The consistent release of deep technical content alongside product updates suggests the team is deliberately targeting developers building production agent systems, not just evaluating vector databases.

◆ Prediction

Engram moving from guide to GA release is the most predictable next step. The experimental Search REST API, introduced in 1.39, is also positioned to stabilize — and the growing late-interaction retrieval work (multi-vector for PDFs and charts) looks like the foundation of a more formal multi-modal retrieval product rather than staying at the technique level.

Alternatives to GraphHopper and Weaviate

Other DevOps products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either GraphHopper or Weaviate.

See all GraphHopper alternatives → · See all Weaviate alternatives →

Recent activity from GraphHopper and Weaviate

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoWeaviateAgent Memory with Engram: A Practical Guide
  2. 6d agoWeaviate4-bit Rotational Quantization
  3. 14d agoWeaviateHFresh: Memory-Efficient Vector Search
  4. 15d agoWeaviateBuilding Foundry Part 3: From archive to creative search
  5. 22d agoWeaviateHow to extract meaning from charts and tables in PDFs
  6. 27d agoWeaviateWeaviate 1.39: Boost API and MMR diversity hit GA, experimental Search REST API ships
  7. 11mo agoGraphHopper11.0 refines mode-specific OSM tag handling and adds POST /navigate
  8. 1y agoGraphHopper10.2 fixes an import failure on recent OSM turn restriction data
  9. 1y agoGraphHopper10.1 cherry-picks a via-way turn restriction fix
  10. 1y agoGraphHopper10.0 reworks edge storage layout and turn cost computation
  11. 2y agoGraphHopper9.1 is a bugfix release with no documented changes
  12. 2y agoGraphHopperVehicle profiles collapse into custom models in GraphHopper 9

Frequently asked questions

What is the difference between GraphHopper and Weaviate?

They serve adjacent needs but don't currently overlap on shipped themes. Weaviate is currently shipping more aggressively (velocity 8.8 vs 0.0), with 3 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is GraphHopper better than Weaviate?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Weaviate is currently shipping more aggressively (velocity 8.8 vs 0.0), with 3 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.

What are the best alternatives to GraphHopper?

Top GraphHopper alternatives in DevOps are ranked by recent ship velocity. Browse the "GraphHopper alternatives" section above for the current picks, or visit /alternatives/graphhopper for the full list with editorial commentary on each.

What are the best alternatives to Weaviate?

Top Weaviate alternatives in DevOps are ranked by recent ship velocity. Browse the "Weaviate alternatives" section above for the current picks, or visit /alternatives/weaviate for the full list with editorial commentary on each.