Looker
Looker's release feed is mostly page furniture; the shipping behind it is thin.
A side-by-side editorial comparison of Neo4j and Plotly — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Neo4j | Plotly |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 7.5 | 0.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | mcp, cypher, vector-search, aura | dash-hosting, plotly-cloud, custom-domains, compute-credits |
| Last editorial update | 1d ago | 11h ago |
| Website | — | Visit → |
Neo4j is wiring Aura for agents that query the graph directly, not for humans writing Cypher.
Aura's monthly database releases continue to track the GQL standard — July adds an explicit GROUP BY subclause and a cardinality() function to Cypher 25, and takes quantized vector search to GA with scalar quantization as the default for new indexes. Around the database, the platform work is heavier: a hosted MCP service, a Cypher Copilot that validates its own output, Document Intelligence for turning unstructured files into a graph model, and REST APIs for user lifecycle management.
The desktop app builder is pre-1.0, but Plotly Cloud quietly turned into a Dash hosting platform.
Two releases in this window build out Plotly Cloud as real hosting rather than a preview environment: compute modes and app sizing put a sleep-versus-always-awake dial and a resource tier on every app, and custom domains let teams serve Dash apps on a hostname they own, with DNS verification and TLS provisioning handled for them. The paid boundary sits on that line — .plotly.app URLs are free, owned domains are Pro and above. Plotly Studio meanwhile ticks through 0.0.82 to 0.0.85 with saved credentials, Winget distribution, breadcrumb navigation and a confirmation step before automatic secret redaction.
Aura's monthly database releases continue to track the GQL standard — July adds an explicit GROUP BY subclause and a cardinality() function to Cypher 25, and takes quantized vector search to GA with scalar quantization as the default for new indexes. Around the database, the platform work is heavier: a hosted MCP service, a Cypher Copilot that validates its own output, Document Intelligence for turning unstructured files into a graph model, and REST APIs for user lifecycle management.
The centre of gravity has moved from the query language to the access path. MCP for Aura, Copilot's self-correcting generation, and Document Intelligence all point at the same conclusion: Neo4j expects most new graph traffic to originate from an AI client rather than a developer's editor. The Cypher work still lands monthly, but it is now infrastructure under an agent-facing surface.
Expect MCP for Aura to extend past its current Free/Professional/Business Critical tiers to Virtual Dedicated Cloud, and Document Intelligence to leave preview with the same conversational model-building loop attached to the graph it produces.
Two releases in this window build out Plotly Cloud as real hosting rather than a preview environment: compute modes and app sizing put a sleep-versus-always-awake dial and a resource tier on every app, and custom domains let teams serve Dash apps on a hostname they own, with DNS verification and TLS provisioning handled for them. The paid boundary sits on that line — .plotly.app URLs are free, owned domains are Pro and above. Plotly Studio meanwhile ticks through 0.0.82 to 0.0.85 with saved credentials, Winget distribution, breadcrumb navigation and a confirmation step before automatic secret redaction.
The centre of gravity has moved from the desktop tool to the hosting product. Studio's releases are pre-1.0 hardening — navigation, credential handling, install paths — while Cloud is the side gaining capability that changes what a customer can do, and it is where the tier boundaries are being drawn. Consumption economics are becoming explicit, with idle spend and cold starts surfaced as customer-tunable settings rather than hidden platform behaviour.
The next Cloud releases most likely extend the resource and access controls a hosted app needs — finer app sizing, or authentication and access rules on custom domains — rather than adding capability to Studio.
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 Plotly.
Looker's release feed is mostly page furniture; the shipping behind it is thin.
Fulcrum is retiring Google Maps for Esri and stabilising the ArcGIS stack behind it.
Shynet went silent for two and a half years and a security audit is what woke it up.
Power BI's monthly grind: authoring defaults, DAX documentation, and cleaner axes.
BigQuery is making itself agent-callable and pulling inference inside the SQL boundary.
Lightdash is turning BI into an app platform its users' coding agents can build against.
See all Neo4j alternatives → · See all Plotly 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 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 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 Plotly alternatives in Analytics are ranked by recent ship velocity. Browse the "Plotly alternatives" section above for the current picks, or visit /alternatives/plotly for the full list with editorial commentary on each.