Cody
Cody batches nine ecommerce UX and analytics improvements into a single September release
A side-by-side editorial comparison of Bagisto and Spryker — 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.
Spryker's changelog feed is currently capturing documentation pages rather than discrete releases.
The recent feed is dominated by feature-overview and integration-guide pages — Customer Account Management, Merchant users, Marketplace Merchant Portal, IAM, MFA, PunchOut Gateway — rather than dated release announcements. What's being surfaced reflects Spryker's B2B and marketplace footprint: Back Office for operators, Merchant Portal for sellers, MFA and IAM for the security layer, PunchOut for procurement integration. None of these entries describe a fresh capability — they describe what already exists.
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 recent feed is dominated by feature-overview and integration-guide pages — Customer Account Management, Merchant users, Marketplace Merchant Portal, IAM, MFA, PunchOut Gateway — rather than dated release announcements. What's being surfaced reflects Spryker's B2B and marketplace footprint: Back Office for operators, Merchant Portal for sellers, MFA and IAM for the security layer, PunchOut for procurement integration. None of these entries describe a fresh capability — they describe what already exists.
Without dated release content, trajectory has to be read from what Spryker is documenting rather than what it's shipping. The doc emphasis on Marketplace, PunchOut, and MFA suggests B2B procurement and merchant onboarding remain the center of gravity. For any move to look directional, this feed would need to start surfacing changelogs rather than evergreen reference pages.
Until the source switches from doc-page captures to release-note entries, classifications will stay trivial regardless of what Spryker actually ships. Once the changelog surface clears up, expect commentary to focus on Marketplace operator features and the PunchOut integration matrix.
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 Spryker.
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 Spryker alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Bagisto and Spryker are shipping at a similar cadence (velocity 6.3 vs 6.3, 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. Bagisto and Spryker are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). 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 Spryker alternatives in E-comm are ranked by recent ship velocity. Browse the "Spryker alternatives" section above for the current picks, or visit /alternatives/spryker for the full list with editorial commentary on each.