Cody
Cody batches nine ecommerce UX and analytics improvements into a single September release
A side-by-side editorial comparison of GrandNode and Virto Commerce — release velocity, themes, recent moves, and the top alternatives to consider.
GrandNode rebuilt itself into modules — then the release feed went quiet for a year.
GrandNode ships one substantial beta per .NET major version, and the last one, 2.3.0, was the most structural: the monolith split into installable modules for installation, migration, API and scheduled tasks, each toggleable from appsettings, and the API layer dropped OData and Swagger for OpenAPI and Scalar. Nothing has appeared in the feed since that release in early 2025.
Virto Commerce backports a blade widget UI freeze fix across three active release trains while tightening module auth hooks
Virto Commerce is simultaneously maintaining multiple release trains (3.1007, 3.1039, 3.1060, 3.1068-3.1070), applying the same fixes as backports across the board. The current batch addresses a UI freeze in blade widget containers triggered by repeated sign-in, pipeline hooks for routing and authentication lifecycle events, and a security fix ensuring user deletion targets only by ID. The multi-branch model reflects an enterprise customer base spread across versions.
GrandNode ships one substantial beta per .NET major version, and the last one, 2.3.0, was the most structural: the monolith split into installable modules for installation, migration, API and scheduled tasks, each toggleable from appsettings, and the API layer dropped OData and Swagger for OpenAPI and Scalar. Nothing has appeared in the feed since that release in early 2025.
The arc across these four betas is consistent decomposition. Each cycle pulls something out of the core — database providers, the vendor portal, template handling, then the installation and API subsystems themselves — and re-lands it as a separable piece. Payments moved the same way, with Stripe Checkout replacing the bundled PayPal plugin. The direction is clear; the cadence is not, and roughly a year of silence in the feed is the more significant fact right now.
The entries establish a rhythm of one beta per ASP.NET Core major, which would point at a .NET 10 cycle next, but nothing in this changelog indicates whether that work is underway — the gap since 2.3.0 is unexplained here.
Virto Commerce is simultaneously maintaining multiple release trains (3.1007, 3.1039, 3.1060, 3.1068-3.1070), applying the same fixes as backports across the board. The current batch addresses a UI freeze in blade widget containers triggered by repeated sign-in, pipeline hooks for routing and authentication lifecycle events, and a security fix ensuring user deletion targets only by ID. The multi-branch model reflects an enterprise customer base spread across versions.
Module pipeline hooks — firing after routing and after authentication — represent a meaningful extension to the developer API, giving module authors reliable lifecycle callbacks. The bounded API key lookup cache and dedup notifier hot-path optimizations point to ongoing performance work on the auth layer.
Pipeline hook coverage will likely expand to more module lifecycle events in coming releases; the security-focused user-deletion fix (by ID only) suggests a broader audit of identifier handling across the platform may be underway.
Other E-comm 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 GrandNode or Virto Commerce.
Cody batches nine ecommerce UX and analytics improvements into a single September release
Shopify overhauled its admin shell and pulled Meta into its AI commerce channel layer.
Foxy is steadily expanding its payment and shipping provider integrations via API, with FedEx OAuth and PayPal improvements leading recent work.
Snipcart's changelog is documentation pages—an MCP server and robust API suggest active developer-focused platform work, but no release timeline is visible.
CS-Cart ships one major version per quarter on a steady, predictable cycle with minimal public changelog detail.
Antavo's changelog is all thought leadership — the product roadmap is not visible in these entries.
See all GrandNode alternatives → · See all Virto Commerce alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — ecommerce — within E-comm. Virto Commerce is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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. Virto Commerce is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other E-comm products to evaluate alongside.
Top GrandNode alternatives in E-comm are ranked by recent ship velocity. Browse the "GrandNode alternatives" section above for the current picks, or visit /alternatives/grandnode for the full list with editorial commentary on each.
Top Virto Commerce alternatives in E-comm are ranked by recent ship velocity. Browse the "Virto Commerce alternatives" section above for the current picks, or visit /alternatives/virto-commerce for the full list with editorial commentary on each.