Shopify
Shopify keeps taking chores off the merchant's desk, now including translation upkeep.
A side-by-side editorial comparison of Foxy and Hi.Events — release velocity, themes, recent moves, and the top alternatives to consider.
Foxy locks down its legacy API as the security cleanup reaches customers.
Foxy's changelog is a steady run of small fixes across payments, shipping carriers and store settings. The past three weeks have centered on secrets handling: committed AWS credentials removed, encryption keys moved to a key provider, and now restricted legacy API access for stores still on old FoxyShop store secrets.
Hi.Events 2.0 ends single-date events: recurring occurrences, embedded checkout, a REST API.
Hi.Events is in release candidates for 2.0, its largest release so far. rc.1 made every event a set of occurrences generated from recurrence rules, and added embedded checkout, product add-ons, a rebuilt check-in app, a documented REST API and a redesigned dashboard, with one-way migrations. rc.2 adds per-date ticket quantities, sequential tier release, AI event moderation and a site-wide cookie banner. The 1.x line before it shipped security fixes for webhook SSRF and spreadsheet formula injection.
Foxy's changelog is a steady run of small fixes across payments, shipping carriers and store settings. The past three weeks have centered on secrets handling: committed AWS credentials removed, encryption keys moved to a key provider, and now restricted legacy API access for stores still on old FoxyShop store secrets.
The security pass has moved from internal hygiene to changes that customers will notice. Restricting the legacy API is the first item in this run that can break an existing integration. Outside that, the work is API parity and connector maintenance, with no new product surface.
Expect more restrictions or deprecations aimed at legacy credentials and API paths, probably with migration guidance for affected FoxyShop stores. The entries show no sign of a larger feature release.
Hi.Events is in release candidates for 2.0, its largest release so far. rc.1 made every event a set of occurrences generated from recurrence rules, and added embedded checkout, product add-ons, a rebuilt check-in app, a documented REST API and a redesigned dashboard, with one-way migrations. rc.2 adds per-date ticket quantities, sequential tier release, AI event moderation and a site-wide cookie banner. The 1.x line before it shipped security fixes for webhook SSRF and spreadsheet formula injection.
The project is moving from a single-event ticketing tool to a platform for organisers who run repeating events and sell through their own sites. Embedded checkout and a public API widen where tickets get sold; AI moderation and the security work point to running a hosted, multi-organiser service.
Expect further rc builds that fill gaps in the recurring-event model (per-date inventory came in rc.2) before a 2.0 stable release.
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 Foxy or Hi.Events.
Shopify keeps taking chores off the merchant's desk, now including translation upkeep.
Solidus admin 0.4.1 closes a stored XSS on a customer page.
Virto Commerce moves its MySQL default to 8.4 LTS as Stable 16 approaches.
After Instant Checkout, CartFlows spends a morning patching its sibling plugins.
Antavo's feed turns to Shopify, but it is still a blog, not a changelog.
Cody rebuilds checkout APIs and the customer view while keeping Google prices in sync.
See all Foxy alternatives → · See all Hi.Events alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Foxy is currently shipping more aggressively (velocity 5.0 vs 2.5), 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. Foxy is currently shipping more aggressively (velocity 5.0 vs 2.5), 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 Foxy alternatives in E-comm are ranked by recent ship velocity. Browse the "Foxy alternatives" section above for the current picks, or visit /alternatives/foxy for the full list with editorial commentary on each.
Top Hi.Events alternatives in E-comm are ranked by recent ship velocity. Browse the "Hi.Events alternatives" section above for the current picks, or visit /alternatives/hi-events for the full list with editorial commentary on each.