Fulcrum vs Neo4j
Side-by-side trajectory, velocity, and editorial themes.
Fulcrum ships steadily, but this cycle is maintenance, not direction
Fulcrum is in a maintenance-heavy stretch across its mobile and web field-data-collection apps. The recent releases are dominated by reliability fixes — ArcGIS connectivity, WMS layers requiring token headers, SSO sync errors, offline layer downloads — with a handful of small usability additions like an always-on map scale bar and the ability to background a GPS track before it collects points.
The arc here is incremental hardening of the mapping and GPS core rather than a capability expansion. The repeated ArcGIS and WMS fixes across Android, iOS, and web suggest a concerted push to stabilize enterprise GIS integrations, likely in response to customer-reported friction. Nothing in this window points to a new product direction.
Expect continued phased mobile releases focused on GIS integration reliability and offline sync; the entries don't support a confident call on any larger feature bet.
Neo4j bends Aura toward GenAI: unstructured docs in, queryable graphs out
Neo4j's changelog is almost entirely Aura, its managed cloud. The last month layers two things onto the graph core at once: GenAI-facing ingestion (document-to-graph, vector datatypes, natural-language query) and enterprise plumbing (user-management APIs, project lifecycle, engine concurrency fixes).
The clear direction is lowering the barrier to graph adoption for AI builders — turning PDFs and DOCX into a modeled graph and letting users query in plain language rather than Cypher. In parallel, the Aura API is maturing into something DevOps and IAM teams can automate against, which is the groundwork for larger enterprise footprints.
Expect Document Intelligence to move from preview toward general availability and to tie more tightly to the vector/embedding import path, positioning Aura as a retrieval backend for GenAI apps.
See more alternatives to Fulcrum →
See more alternatives to Neo4j →