Cody
Cody batches nine ecommerce UX and analytics improvements into a single September release
A side-by-side editorial comparison of Bagisto and Saleor — release velocity, themes, recent moves, and the top alternatives to consider.
Bagisto v2.5.0 adds PostgreSQL support and a full stack upgrade to Laravel 13 + PHP 8.4 + Tailwind 4.
Bagisto is an open-source Laravel-based e-commerce platform currently in the v2.5.0 beta cycle. The headline v2.5.0-beta1 addition is PostgreSQL support via a database grammar abstraction layer — Bagisto was previously MySQL-only, which was a deployment blocker for teams on managed Postgres infrastructure. The same release bundles Laravel 13, PHP 8.4, Pest 5, and Tailwind CSS 4, making it one of the most comprehensive stack upgrades the project has shipped.
Saleor's public feed shows release tags, not what's in them.
The 3.23 line moves through release candidates — 3.23.26-rc.0 and rc.1 landed hours apart on August 6 — but only one entry in the window carries an actual change list. That entry, 3.23.22-rc.0, shows the shape of the work: an identifier field on the Webhook model, a unique tie-breaker for default cursor pagination, and a setting to block customer and anonymous traffic. The other tags publish with nothing but the release commit reference.
Bagisto is an open-source Laravel-based e-commerce platform currently in the v2.5.0 beta cycle. The headline v2.5.0-beta1 addition is PostgreSQL support via a database grammar abstraction layer — Bagisto was previously MySQL-only, which was a deployment blocker for teams on managed Postgres infrastructure. The same release bundles Laravel 13, PHP 8.4, Pest 5, and Tailwind CSS 4, making it one of the most comprehensive stack upgrades the project has shipped.
Bagisto is targeting enterprise and cloud-hosted deployments with the PostgreSQL move, removing the database constraint that limited adoption on platforms where Postgres is the default (AWS RDS, Supabase, Heroku). The full-stack version upgrade signals a focus on staying current with the Laravel ecosystem rather than accumulating technical debt. v2.4.0 also removed visitor tracking entirely and upgraded the upgrade guide with breaking-change documentation — a pattern of deliberate architectural pruning.
v2.5.0 stable will likely follow the beta cycle with database-compatibility testing across MySQL and PostgreSQL as the primary release gate; the Tailwind 4 migration may drive a round of UI theme updates from community contributors.
The 3.23 line moves through release candidates — 3.23.26-rc.0 and rc.1 landed hours apart on August 6 — but only one entry in the window carries an actual change list. That entry, 3.23.22-rc.0, shows the shape of the work: an identifier field on the Webhook model, a unique tie-breaker for default cursor pagination, and a setting to block customer and anonymous traffic. The other tags publish with nothing but the release commit reference.
What is visible is maintenance-grade hardening of an established GraphQL commerce API: pagination determinism, webhook identity, traffic gating. The rc.0-then-rc.1 pattern within a single day suggests a candidate being corrected rather than a feature train, and the point release cadence within 3.23 indicates the branch is in stabilisation rather than expansion.
Expect the 3.23 line to keep issuing patch-level release candidates on this pattern. The feed itself is the limiting factor here — most tags publish without a change list, so feature direction is not derivable from what is being crawled.
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 Bagisto or Saleor.
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.
Virto Commerce backports a blade widget UI freeze fix across three active release trains while tightening module auth hooks
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.
See all Bagisto alternatives → · See all Saleor alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Bagisto is currently shipping more aggressively (velocity 6.3 vs 5.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. Bagisto is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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 Bagisto alternatives in E-comm are ranked by recent ship velocity. Browse the "Bagisto alternatives" section above for the current picks, or visit /alternatives/bagisto for the full list with editorial commentary on each.
Top Saleor alternatives in E-comm are ranked by recent ship velocity. Browse the "Saleor alternatives" section above for the current picks, or visit /alternatives/saleor for the full list with editorial commentary on each.