Froxlor
Froxlor's bugfix releases now describe their changes, and most are security fixes.
A side-by-side editorial comparison of Nominatim and TypeDB — release velocity, themes, recent moves, and the top alternatives to consider.
Nominatim 5.3.3 turns off its debug view by default because it can leak server details.
Nominatim releases a minor every few months with hotfixes when the update path breaks. 5.3.3, the first entry since April, restores compatibility with the latest SQLAlchemy and fixes reverse geocoding near overlapping POIs, POIs parented to unnamed streets, TIGER parent streets and rank-11 boundaries. It also tightens API parameter validation, output escaping and overlong query terms, and makes one breaking change: the debug view is now off unless NOMINATIM_SERVE_DEBUG_OUTPUT is set.
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.
Nominatim releases a minor every few months with hotfixes when the update path breaks. 5.3.3, the first entry since April, restores compatibility with the latest SQLAlchemy and fixes reverse geocoding near overlapping POIs, POIs parented to unnamed streets, TIGER parent streets and rank-11 boundaries. It also tightens API parameter validation, output escaping and overlong query terms, and makes one breaking change: the debug view is now off unless NOMINATIM_SERVE_DEBUG_OUTPUT is set.
Since the move to a Python package was completed in 5.0, releases have concentrated on geocoding quality and the update pipeline. 5.3.3 adds a security-minded layer, validating and escaping API input and output and closing the debug view, which suggests operators running public instances are now a design concern. No migrations are needed, keeping upgrades cheap.
Expect a 5.4 minor to continue query-parser and update-pipeline work; the hardening in 5.3.3 may extend to further API defaults.
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 Nominatim or TypeDB.
Froxlor's bugfix releases now describe their changes, and most are security fixes.
GraphHopper 11.1 is a security release, and 12.0 prerelease tags have started.
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 Nominatim 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 Nominatim alternatives in DevOps are ranked by recent ship velocity. Browse the "Nominatim alternatives" section above for the current picks, or visit /alternatives/nominatim 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.