Froxlor
Froxlor's bugfix releases now describe their changes, and most are security fixes.
A side-by-side editorial comparison of GraphHopper and TypeDB — release velocity, themes, recent moves, and the top alternatives to consider.
GraphHopper 11.1 is a security release, and 12.0 prerelease tags have started.
GraphHopper published 11.1 in October as a security release fixing what it calls critical vulnerabilities, without describing them; the attached change list largely repeats 11.0's OSM tag work, plus items such as trip-based public transit routing, scriptable turn penalties and POST /navigate. Alongside it, 12.0-pre1 and 12.0-pre3 tags and an odd 11.0-alpha1 tag appeared with only commit messages. The roughly yearly major cadence (10.0 in late 2024, 11.0 in October 2025) points at 12.0 as the next major.
TypeDB 3.14 is spent on import safety and query correctness, not new syntax.
TypeDB went from 3.13.6 to 3.14.1 in a month, skipping a 3.14.0 final. 3.14.1 rejects imported relations that have no role players, which TypeDB can't store and would otherwise lose, fixes a query-plan cache leak that grew without bound during write-only imports, and checkpoints imported databases before serving them to avoid replaying gigabytes of commits. The 3.14 candidates also reworked attribute comparisons, fixing missed answers across value types and turning some runtime panics into compile-time errors.
GraphHopper published 11.1 in October as a security release fixing what it calls critical vulnerabilities, without describing them; the attached change list largely repeats 11.0's OSM tag work, plus items such as trip-based public transit routing, scriptable turn penalties and POST /navigate. Alongside it, 12.0-pre1 and 12.0-pre3 tags and an odd 11.0-alpha1 tag appeared with only commit messages. The roughly yearly major cadence (10.0 in late 2024, 11.0 in October 2025) points at 12.0 as the next major.
The engine's recent work is routing quality, reading OSM tags more faithfully per mode, and that continues in the 11.x list. The 12.0 prereleases suggest the next major is in preparation, but their notes give no content. Security disclosure is thin: 11.1 is labelled critical without naming the issue.
A 12.0 release is the next likely major entry given the prerelease tags; its contents can't be read from these entries.
TypeDB went from 3.13.6 to 3.14.1 in a month, skipping a 3.14.0 final. 3.14.1 rejects imported relations that have no role players, which TypeDB can't store and would otherwise lose, fixes a query-plan cache leak that grew without bound during write-only imports, and checkpoints imported databases before serving them to avoid replaying gigabytes of commits. The 3.14 candidates also reworked attribute comparisons, fixing missed answers across value types and turning some runtime panics into compile-time errors.
The work since the batch-query given stage in July has moved from capability to correctness. Import and export, which matter for clustered and migrated deployments, are being made safe at scale, and the query planner is being made to return complete answers when types are mixed. 3.13.6 added fully qualified built-in function names as a first step toward namespacing future functions.
Expect more built-in functions under a std namespace, since 3.13.6 says most future functions will need it. The rejection of role-player-less relations is described as temporary until an explicit independent annotation for relations exists.
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 TypeDB.
Froxlor's bugfix releases now describe their changes, and most are security fixes.
Nominatim 5.3.3 turns off its debug view by default because it can leak server details.
Syncope runs two IAM branches in lockstep, but ships announcements with no change detail.
RaspAP folded its Insiders-only features into the open release, then rebuilt its VPN handling.
Exoscale is filling in cloud basics: VPC, lifecycle rules and cheaper IPv6 load balancing.
NSD's 4.15 line is being shaped by outside researchers' bug reports.
See all GraphHopper alternatives → · See all TypeDB alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. TypeDB is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. TypeDB is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 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.
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.
Top TypeDB alternatives in DevOps are ranked by recent ship velocity. Browse the "TypeDB alternatives" section above for the current picks, or visit /alternatives/typedb for the full list with editorial commentary on each.