OpenCTI
OpenCTI is rebuilding its connector layer into a marketplace and wiring the platform to XTM Hub
Comparison · Analytics
Amundsen vs Neo4j
A side-by-side editorial comparison of Amundsen and Neo4j — release velocity, themes, recent moves, and the top alternatives to consider.
Amundsen vs Neo4j: at a glance
| Feature | Amundsen | Neo4j |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 7.5 |
| Sparks · 30d | 0 | 1 |
| Top themes | data-catalog, metadata, maintenance-mode, monorepo-releases | graph-database, mcp, cypher-copilot, aura-cloud |
| Last editorial update | 16h ago | 6d ago |
| Website | Visit → | — |
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.
What is Neo4j?
Neo4j is making the graph legible to agents and comfortable for humans at the same time.
The window carries two distinct threads. On the AI side: an MCP server for Aura, Cypher Copilot gaining baseline edits and in-editor review, and a Document Intelligence preview for getting unstructured content into the graph. On the platform side: the July Aura release, Enterprise Studio 2026.07, self-service SSO, Fleet Manager migration from Community Edition to Aura, and now persistent query tabs in the Query tool.
Amundsen vs Neo4j: editorial side-by-side
Amundsen
0.0ANALYTICS
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.
Neo4j
7.5ANALYTICS
Neo4j is making the graph legible to agents and comfortable for humans at the same time.
◆ Current state
The window carries two distinct threads. On the AI side: an MCP server for Aura, Cypher Copilot gaining baseline edits and in-editor review, and a Document Intelligence preview for getting unstructured content into the graph. On the platform side: the July Aura release, Enterprise Studio 2026.07, self-service SSO, Fleet Manager migration from Community Edition to Aura, and now persistent query tabs in the Query tool.
◆ Where it's heading
Neo4j is answering the question of who writes Cypher by making the answer 'not necessarily a person'. MCP exposes Aura to assistants, Copilot writes and reviews queries in the editor, and Document Intelligence handles the ingestion step that used to require a pipeline project. Around that, the managed-service work — SSO, fleet migration, release cadence — is aimed at moving self-managed installations into Aura, where those AI surfaces live.
◆ Prediction
With MCP shipped and Copilot writing queries, the missing piece is governance over what an agent may run against a production graph — expect permissions or review controls scoped to AI-issued Cypher, and continued pressure to migrate Community Edition users into Aura.
Alternatives to Amundsen and Neo4j
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 Neo4j.
Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
Omni
Omni ships weekly, and almost every week the headline item is an AI feature
OpenDataDiscovery
Four ODD Platform releases in two weeks, and not one of them changes the product
Apache Baremaps
Baremaps got geoparquet and hillshading, then went quiet for eighteen months in incubation
Deequ
Deequ ships GitHub tags whose release notes are one commit message long
See all Amundsen alternatives → · See all Neo4j alternatives →
Recent activity from Amundsen and Neo4j
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 6d agoNeo4jQuery Tabs: A new way to work with your queries
- 7d agoNeo4jAura July: explicit GROUP BY in Cypher, quantized vectors GA
- 11d agoNeo4jEnterprise Studio 2026.07 collects Bloom and dashboard fixes
- 20d agoNeo4jMCP for Aura Now Available ⚡
- 21d agoNeo4jCypher Copilot updates: Smarter Queries, Baseline Edits, and In-Editor Review
- 27d agoNeo4jFleet Manager: Migrate a Community Edition database to Aura
- 1y agoAmundsenDatabuilder 7.5.1 adds implicit-transaction config for the neo4j extractor
- 2y agoAmundsenDatabuilder 7.5.0 is dependency bumps and a Python 3.10 matrix
- 2y agoAmundsenMetadata 3.13.0 adds aggregating alerts and a gremlin proxy lookup
- 2y agoAmundsenFrontend 4.3.0 republishes the same changelog under a second tag
- 2y agoAmundsenCommon 0.32.0 republishes the same changelog under a third tag
- 2y agoAmundsenMetadata 3.12.3 clears frontend dependency vulnerabilities
Frequently asked questions
What is the difference between Amundsen and Neo4j?
They serve adjacent needs but don't currently overlap on shipped themes. Neo4j is currently shipping more aggressively (velocity 7.5 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 Neo4j?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Neo4j is currently shipping more aggressively (velocity 7.5 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 Neo4j?
Top Neo4j alternatives in Analytics are ranked by recent ship velocity. Browse the "Neo4j alternatives" section above for the current picks, or visit /alternatives/neo4j for the full list with editorial commentary on each.