Omni
Omni ships weekly, and almost every week the headline item is an AI feature
A side-by-side editorial comparison of Amundsen and OR-Tools — release velocity, themes, recent moves, and the top alternatives to consider.
Amundsen's last release was a config flag, and the feed has been silent for two years
Amundsen ships as several separately versioned components — databuilder, metadata, frontend, common — cut from one repository, and the release feed shows the same changelog republished under three different component tags on the same afternoon. Reading past the tag names, the content is overwhelmingly dependabot bumps, Python compatibility-matrix maintenance and mypy upgrades, with real features appearing a couple of times a year. The final release, databuilder 7.5.1 in August 2024, contains exactly one change: a config option for implicit transactions in the neo4j extractor.
Google's solver suite where nearly every release note is really about CP-SAT.
OR-Tools bundles constraint programming, linear solvers, routing, and graph algorithms, but the release notes make the priority obvious: CP-SAT gets the most substantive changes in every version, particularly its no_overlap_2d propagation, presolve, and cut management. Around that core, the work is platform and dependency maintenance — new Linux distro support, Python and Java version cycling, and bumping the bundled Coin-OR, HiGHS, SCIP, and abseil versions. Note that these entries carry batch-stamped crawl dates; the newest actual release here is v9.12 from early 2025.
Amundsen ships as several separately versioned components — databuilder, metadata, frontend, common — cut from one repository, and the release feed shows the same changelog republished under three different component tags on the same afternoon. Reading past the tag names, the content is overwhelmingly dependabot bumps, Python compatibility-matrix maintenance and mypy upgrades, with real features appearing a couple of times a year. The final release, databuilder 7.5.1 in August 2024, contains exactly one change: a config option for implicit transactions in the neo4j extractor.
The direction is contraction. Python 3.7 support was dropped and the matrix narrowed to 3.8 and 3.9 before 3.10 was cautiously added to everything except the metadata service, contributor names moved to emeritus status, and organisations were removed from the README's adopter list. What feature work exists is small and peripheral — a PowerBI logo, aggregated alerts, a gremlin proxy method — rather than anything touching how the catalog works. Nothing has been published since August 2024.
There is no signal in these entries of planned work, and a two-year silence following a single-flag release means the practical expectation is no further releases; the component version skew across databuilder, metadata and frontend is now frozen where it stopped.
OR-Tools bundles constraint programming, linear solvers, routing, and graph algorithms, but the release notes make the priority obvious: CP-SAT gets the most substantive changes in every version, particularly its no_overlap_2d propagation, presolve, and cut management. Around that core, the work is platform and dependency maintenance — new Linux distro support, Python and Java version cycling, and bumping the bundled Coin-OR, HiGHS, SCIP, and abseil versions. Note that these entries carry batch-stamped crawl dates; the newest actual release here is v9.12 from early 2025.
The suite is consolidating on fewer, better-maintained components: old graph classes were removed outright, MathOpt got a deep rework and shipped in the Python wheel, and the Python API was rewritten to PEP 8 naming. Build-level changes point the same direction — dependencies split into separate shared libraries, Windows output moved to DLLs.
CP-SAT scheduling and 2D packing propagation should keep absorbing the bulk of the effort; the entries show no other component receiving comparable sustained investment.
Other Analytics 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 Amundsen or OR-Tools.
Omni ships weekly, and almost every week the headline item is an AI feature
Four ODD Platform releases in two weeks, and not one of them changes the product
Baremaps got geoparquet and hillshading, then went quiet for eighteen months in incubation
Deequ ships GitHub tags whose release notes are one commit message long
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
LinkedIn's Iceberg control plane, shipping one pull request per release.
See all Amundsen alternatives → · See all OR-Tools alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Amundsen and OR-Tools are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. Amundsen and OR-Tools are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top Amundsen alternatives in Analytics are ranked by recent ship velocity. Browse the "Amundsen alternatives" section above for the current picks, or visit /alternatives/amundsen for the full list with editorial commentary on each.
Top OR-Tools alternatives in Analytics are ranked by recent ship velocity. Browse the "OR-Tools alternatives" section above for the current picks, or visit /alternatives/or-tools for the full list with editorial commentary on each.