Fulcrum
Fulcrum launches MCP + AI Toolkit in Labs, giving AI assistants the ability to build and query Fulcrum forms directly.
A side-by-side editorial comparison of Mage and Neo4j — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Mage | Neo4j |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 7.5 |
| Sparks · 30d | 0 | 1 |
| Top themes | data-pipelines, orchestration, cadence-decline, dependency-pinning | graph-database, agentic, data-warehouse, abac |
| Last editorial update | 1mo ago | 10d ago |
| Website | Visit → | — |
Feature releases every two months in 2024; one bugfix release in the last twelve.
The release cadence has collapsed. Through 2024 Mage shipped roughly every two months with substantial features each time — memory management rework, dynamic blocks, new sources and destinations, Python 3.11 and 3.12 support. 2025 produced two releases. The most recent entry, 0.9.79 in January 2026, contains no feature section at all: it is dependency pinning, SQLAlchemy 2.0 compatibility, character escaping during code interpolation, and log file handle cleanup. Nothing has followed it in the six months since.
Neo4j's Virtual Graph lets you run Cypher against Snowflake and BigQuery without moving any data.
Neo4j is expanding Aura's geographic reach (AWS London and Montreal this week) while pushing two substantial capability betas: Virtual Graph — a zero-copy bridge that translates Cypher to SQL against BigQuery, Databricks, and Snowflake — and Multiple Databases in a single instance. The August release also shipped native UUID types in Cypher 25 and ABAC for fine-grained access control.
The release cadence has collapsed. Through 2024 Mage shipped roughly every two months with substantial features each time — memory management rework, dynamic blocks, new sources and destinations, Python 3.11 and 3.12 support. 2025 produced two releases. The most recent entry, 0.9.79 in January 2026, contains no feature section at all: it is dependency pinning, SQLAlchemy 2.0 compatibility, character escaping during code interpolation, and log file handle cleanup. Nothing has followed it in the six months since.
The arc runs from expanding the product to keeping it compiling. The 2024 releases added capability — a canvas rework, multi-project support, streaming sinks, Kubernetes job parameters. The 2025 releases shifted toward integrations and CVE response, including a batch of path traversal fixes carrying assigned identifiers. The last release is entirely defensive, including vendoring croniter into the repository and locking scikit-learn to stop upstream changes from breaking builds. That is the profile of a codebase being kept viable rather than developed.
The entries give no basis for predicting the next release — a six-month gap after a dependency-only patch is the only signal available, and nothing here indicates whether the line is paused or finished.
Neo4j is expanding Aura's geographic reach (AWS London and Montreal this week) while pushing two substantial capability betas: Virtual Graph — a zero-copy bridge that translates Cypher to SQL against BigQuery, Databricks, and Snowflake — and Multiple Databases in a single instance. The August release also shipped native UUID types in Cypher 25 and ABAC for fine-grained access control.
Neo4j is positioning itself as the graph layer on top of existing data warehouses rather than a replacement for them. Virtual Graph and ABAC together signal a push into enterprise data architectures where teams have data in Snowflake or BigQuery and want graph traversal without ETL. The multiple-databases GA (coming in months per the release) reinforces that Aura is targeting organizations running multiple isolated tenants on a single cluster.
Virtual Graph will likely exit preview with paid pricing attached once the query-pushdown behavior stabilizes; the next move is probably native support for LLM embedding pipelines that stay in Aura without exporting data to a warehouse.
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 Mage or Neo4j.
Fulcrum launches MCP + AI Toolkit in Labs, giving AI assistants the ability to build and query Fulcrum forms directly.
Holistics is weaving AI governance and proactive alerting into its analytics semantic layer.
Keboola's Kai AI assistant hits GA, completing the pivot from data platform to AI-native pipeline orchestration layer.
Omni's Apps reach general availability, completing its embedded analytics platform pitch.
Lightdash ships AI-generated custom chart types — describe what you want, get a reusable chart type for your whole project.
OpenCTI ships FIPS-validated base images and a new vulnerability data model, targeting enterprise and government deployments.
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 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.
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.
Top Mage alternatives in Analytics are ranked by recent ship velocity. Browse the "Mage alternatives" section above for the current picks, or visit /alternatives/mage-ai for the full list with editorial commentary on each.
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.