← Back to home
Comparison · Analytics

Amundsen vs Hex

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

Amundsen vs Hex: at a glance

FeatureAmundsenHex
SectorAnalyticsAnalytics
Velocity score0.06.3
Sparks · 30d01
Top themesdata-catalog, metadata, maintenance-mode, monorepo-releasesagents, cli, mcp, model-routing
Last editorial update2h ago9h ago
WebsiteVisit →

What is Amundsen?

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.

Read the full Amundsen trajectory →

What is Hex?

Hex is moving its agent out of the notebook and onto programmable surfaces.

Hex ships a fortnightly digest, and the through-line across the last ten is agent reach. The agent now runs from a CLI and API, appears inside Codex, acts as an MCP client against the user's own apps, can search the web, and can see the generative apps it builds. Alongside that, the model layer has become a customer-facing control: a picker, an admin-set default, Auto with visible attribution, and a rotating roster including Fable 5, Kimi K2.7, Claude Opus 5 and GPT-5.6.

Read the full Hex trajectory →

Amundsen vs Hex: editorial side-by-side

A
Amundsen
ANALYTICS
0.0

Amundsen's last release was a config flag, and the feed has been silent for two years

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

H
Hex
ANALYTICS
6.3

Hex is moving its agent out of the notebook and onto programmable surfaces.

◆ Current state

Hex ships a fortnightly digest, and the through-line across the last ten is agent reach. The agent now runs from a CLI and API, appears inside Codex, acts as an MCP client against the user's own apps, can search the web, and can see the generative apps it builds. Alongside that, the model layer has become a customer-facing control: a picker, an admin-set default, Auto with visible attribution, and a rotating roster including Fable 5, Kimi K2.7, Claude Opus 5 and GPT-5.6.

◆ Where it's heading

Hex is positioning the agent as a component other systems call rather than a feature users visit. Governance is being built out in parallel — spend limits, credit usage controls, enterprise role-request controls, signed embedding — which is the pattern of a product preparing for programmatic usage it does not directly supervise. The generative-app surface is drifting the same way, from generated output toward editable, brandable, embeddable artifacts.

◆ Prediction

Expect the CLI and API surface to deepen before the notebook UI gains much, with more of Context Studio and app management reachable programmatically, and expect the spend and role controls to keep pace as headless usage grows.

Alternatives to Amundsen and Hex

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 Hex.

See all Amundsen alternatives → · See all Hex alternatives →

Recent activity from Amundsen and Hex

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

  1. 1d agoHexFast mode, GPT-5.6, and visible model attribution for Auto
  2. 12d agoHexHex Agent becomes callable from the CLI and API
  3. 21d agoHexEditable generative-app code, and an agent that sees what it builds
  4. 28d agoHexMore control over credits, thread metadata, and role requests
  5. 1mo agoHexTwo new models and more controls over generative apps
  6. 1mo agoHexHex in Figma, IAM role support for AWS, and schema refresh history!
  7. 1y agoAmundsenDatabuilder 7.5.1 adds implicit-transaction config for the neo4j extractor
  8. 2y agoAmundsenDatabuilder 7.5.0 is dependency bumps and a Python 3.10 matrix
  9. 2y agoAmundsenMetadata 3.13.0 adds aggregating alerts and a gremlin proxy lookup
  10. 2y agoAmundsenFrontend 4.3.0 republishes the same changelog under a second tag
  11. 2y agoAmundsenCommon 0.32.0 republishes the same changelog under a third tag
  12. 2y agoAmundsenMetadata 3.12.3 clears frontend dependency vulnerabilities

Frequently asked questions

What is the difference between Amundsen and Hex?

They serve adjacent needs but don't currently overlap on shipped themes. Hex is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 Amundsen better than Hex?

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

What are the best alternatives to Amundsen?

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.

What are the best alternatives to Hex?

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