Fulcrum vs Neo4j
Side-by-side trajectory, velocity, and editorial themes.
Field-data captures grow a BI layer while mobile coasts on fixes.
Fulcrum continues steady weekly shipping across web, iOS, and Android, but the substance is concentrated on the web. Recent releases add a freehand lasso selection on maps, a Power BI connector, and time-aware Insights (Beta) queries. Mobile cadence is dominated by single-issue stability fixes rather than new capabilities.
The product is widening from pure field-data capture into the analyze-and-share layer above it. Web work is going into bulk-action ergonomics, BI tooling integration, and growing the Insights surface. Mobile platforms are tracking a maintenance pattern, with versioned releases shipping one or two narrow fixes at a time and no new user-facing capabilities.
Expect Insights to gain depth toward general availability, with more BI-side integrations and richer bulk operations on web selections. Mobile is unlikely to see significant new capabilities in the next cycle.
neo4j-cli ships explicitly for AI agents — Neo4j makes its 'AX' bet concrete.
Neo4j is shipping in three lanes simultaneously: developer/agent surface (the new neo4j-cli covering Aura management, Cypher, and ops, designed for human, developer and agent consumption), Aura cloud capacity and ops (2TB high-memory GCP instances, inactive-member pruning, tighter password policy), and graph analytics maturation (project-level ML model persistence in AGA, Lakehouse export from Microsoft Fabric, Cypher 25 GQL features). Dashboards and Explore are gaining interactivity in parallel.
The arc is toward treating AI agents as a first-class user of the platform, not an integration consumer. Calling out 'AX' alongside DX/UX in the CLI announcement is unusual — most database vendors are still adding MCP servers or chat assistants. Coupled with the GenAI token functions in the April Aura release and AGA's model persistence, Neo4j is consolidating the 'graph as memory substrate for AI agents' position it's been telegraphing for two years.
Likely next: an MCP server fronting the same surface as neo4j-cli, deeper GenAI-native primitives in Cypher 25 (vector ops, embeddings as first-class types), and continued Aura capacity climbs to support larger graph-RAG workloads. Microsoft Fabric integration will probably extend further given the bidirectional Lakehouse work.
See more alternatives to Fulcrum →
See more alternatives to Neo4j →