Citus
Citus keeps three Postgres branches alive while chasing each new major
A side-by-side editorial comparison of Neo4j and OpenSearch Dashboards — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Neo4j | OpenSearch Dashboards |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 7.5 | 0.0 |
| Sparks · 30d | 2 | 0 |
| Top themes | graph-database, mcp, agent-grounding, cypher-copilot | dashboards, vega, dependency-maintenance, patch-branch |
| Last editorial update | 2d ago | 4h ago |
| Website | — | Visit → |
Neo4j is turning the graph into something an agent can query without knowing Cypher.
Neo4j's releases this month converge on one goal: letting AI clients use a graph without a human writing Cypher. MCP for Aura is a hosted Model Context Protocol service built into the platform, with schema, read, and read-write tools and no server to run. Document Intelligence takes the other end — an assistant that reads PDF, DOCX, and EPUB files from cloud storage and proposes the node labels and relationships needed to model them as a graph. Around those, the enterprise track keeps shipping: self-service SSO with per-instance role mapping, Community-to-Aura migration in Fleet Manager, and monthly Enterprise Studio maintenance.
Three releases in a year, all of them about the Vega dependency — the feed shows nothing else.
OpenSearch Dashboards' visible release stream is three 2.19.x patches spread across ten months, and every one of them concerns the Vega visualisation library: a CVE fix in 2.19.5 alongside webpack updates, a vega-lite version revert in 2.19.4, and a release-notes commit for 2.19.3. The entries themselves are raw commit messages and sign-off lines rather than written release notes, so the titles carry the diff subject instead of a description.
Neo4j's releases this month converge on one goal: letting AI clients use a graph without a human writing Cypher. MCP for Aura is a hosted Model Context Protocol service built into the platform, with schema, read, and read-write tools and no server to run. Document Intelligence takes the other end — an assistant that reads PDF, DOCX, and EPUB files from cloud storage and proposes the node labels and relationships needed to model them as a graph. Around those, the enterprise track keeps shipping: self-service SSO with per-instance role mapping, Community-to-Aura migration in Fleet Manager, and monthly Enterprise Studio maintenance.
Cypher is being repositioned from the interface to an implementation detail. Copilot now lints and EXPLAIN-retries its own generated queries and feeds the errors back to the model to correct hallucinated paths and inverted relationship directions — an admission that generated Cypher needs a verification loop before anyone runs it. Combined with the grounded-answers framing on MCP, Neo4j is arguing that a graph is the substrate that keeps agent answers accurate. The operational work reads as clearing the procurement objections that come with that pitch.
Virtual Dedicated Cloud support for MCP for Aura is stated as coming, and Document Intelligence should exit preview. The open question is whether read-write MCP access gains finer-grained permissions than the current three tools, given that IdP group-to-database-role mapping already exists on the SSO side.
OpenSearch Dashboards' visible release stream is three 2.19.x patches spread across ten months, and every one of them concerns the Vega visualisation library: a CVE fix in 2.19.5 alongside webpack updates, a vega-lite version revert in 2.19.4, and a release-notes commit for 2.19.3. The entries themselves are raw commit messages and sign-off lines rather than written release notes, so the titles carry the diff subject instead of a description.
What is visible is a maintenance branch being kept current on one problematic dependency, with the vega-lite revert suggesting the earlier upgrade broke something and had to be backed out. Whether anything else is happening in the project cannot be read from this feed — the release bodies contain no changelog, only commit metadata, which makes this source unreliable for tracking the product.
The entries give no basis for predicting the next move; anyone tracking OpenSearch Dashboards should read the project's own release notes rather than these tags.
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 Neo4j or OpenSearch Dashboards.
Citus keeps three Postgres branches alive while chasing each new major
Kylin ships once a year with empty release notes and a native engine nobody is being told about.
Iceberg's release cadence is now backports and CVE patches across three live minor lines.
Feature releases every two months in 2024; one bugfix release in the last twelve.
MCP servers became first-class governed assets in 1.13.0 — and 2.0 is now in release candidate.
Every release in this window is columnstore work — compression is where TimescaleDB is spending
See all Neo4j alternatives → · See all OpenSearch Dashboards alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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 2 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. Neo4j is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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.
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.
Top OpenSearch Dashboards alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenSearch Dashboards alternatives" section above for the current picks, or visit /alternatives/opensearch-dashboards for the full list with editorial commentary on each.