Virto Commerce
Three maintained branches, one credential bug, and very little else moving.
A side-by-side editorial comparison of Spree Commerce and Wheelhouse — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Spree Commerce | Wheelhouse |
|---|---|---|
| Sector | E-comm | E-comm |
| Velocity score | 5.0 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | headless-commerce, typescript-sdk, react-dashboard, gated-pricing | revenue-management, api-first, mcp, webhooks |
| Last editorial update | 22d ago | 1d ago |
| Website | Visit → | — |
Spree's centre of gravity has moved to the TypeScript SDK and a React admin.
Spree's release feed is now dominated by @spree/sdk, which went stable in April and has shipped three minors since, each pinned to a matching backend version. The 5.6 candidates carry the server-side counterpart: a React Dashboard developer preview shipping as the spree_dashboard host gem alongside the existing Rails gems, and single-node Docker as the default deployment path. The Ruby monolith is still the backend, but the surfaces developers touch are increasingly npm packages.
Wheelhouse is closing the last gaps between its app and the API other companies build on.
Wheelhouse ships API surface faster than app features. The current release rolls segment performance metrics up across every listing a saved segment matches, works across owned and shared or managed listings, and converts monetary metrics into whichever currency the caller asks for. It reaches the same MCP server that already exposes the platform to AI assistants, so the aggregate is available from a prompt as well as an endpoint.
Spree's release feed is now dominated by @spree/sdk, which went stable in April and has shipped three minors since, each pinned to a matching backend version. The 5.6 candidates carry the server-side counterpart: a React Dashboard developer preview shipping as the spree_dashboard host gem alongside the existing Rails gems, and single-node Docker as the default deployment path. The Ruby monolith is still the backend, but the surfaces developers touch are increasingly npm packages.
Two arcs run in parallel. The SDK is absorbing flows that used to require custom backend work — provider-dispatched login against a server-side strategy registry, double opt-in newsletter subscription and token-based unsubscribe, payment sessions across gateways. Meanwhile the API is being made safe for gated commerce: money fields are now typed string or null everywhere, because a prices_hidden channel returns null for every monetary amount including nested records. That is the SDK contract for the wholesale and gated-storefront work landing in 5.6.
Expect 5.6.0 to go stable with the React dashboard still labelled developer preview, and the SDK to keep its lockstep versioning — each minor stating the exact backend release it requires.
Wheelhouse ships API surface faster than app features. The current release rolls segment performance metrics up across every listing a saved segment matches, works across owned and shared or managed listings, and converts monetary metrics into whichever currency the caller asks for. It reaches the same MCP server that already exposes the platform to AI assistants, so the aggregate is available from a prompt as well as an endpoint.
The sequencing is deliberate: expose everything through an API, make it reachable from AI clients, then let it push events out so partners can build without polling. This release is the follow-through on a promise made in July — the aggregated metrics endpoint was announced then, and now covers shared and managed inventory and multi-currency portfolios, which is what property managers running someone else's listings actually need. IntelliHost remains the proof of the model, a third party closing the full pricing loop on Wheelhouse rails.
With webhooks, scoreboards and segment aggregates in place, the remaining gap is write-side automation at portfolio scale rather than per-listing. Expect the partner roster to grow before the app does — the entries consistently describe the API as the product's leading edge.
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 Spree Commerce or Wheelhouse.
Three maintained branches, one credential bug, and very little else moving.
Canix is turning cannabis compliance paperwork into something its AI fills in for you.
ShipHawk's feed is fulfillment thought leadership with no product releases
Shopify pulls retail setup and store analytics onto one Point of Sale page
Shopaccino's tracked feed is a marketing page scrape with no release data in it
Antavo publishes loyalty-program teardowns, not release notes.
See all Spree Commerce alternatives → · See all Wheelhouse alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Spree Commerce and Wheelhouse are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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. Spree Commerce and Wheelhouse are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other E-comm products to evaluate alongside.
Top Spree Commerce alternatives in E-comm are ranked by recent ship velocity. Browse the "Spree Commerce alternatives" section above for the current picks, or visit /alternatives/spree for the full list with editorial commentary on each.
Top Wheelhouse alternatives in E-comm are ranked by recent ship velocity. Browse the "Wheelhouse alternatives" section above for the current picks, or visit /alternatives/wheelhouse for the full list with editorial commentary on each.