Starshipit vs Medusa
Side-by-side trajectory, velocity, and editorial themes.
Starshipit moves up the stack into warehouse management — picking, scanning, and stock alongside its shipping labels.
Starshipit is a multi-carrier shipping platform that has been quietly expanding outside of label generation. The headline move is a built-in warehouse management module covering products and locations, inbound receiving, stock adjustments, pick-pack-ship flows, and barcode scanning on mobile. Around it, the carrier surface keeps growing — UPS third-party duty billing, DHL Express proforma invoices, Asendia and OnSend integrations — and the platform absorbs operational shocks like the Sendle closure with automatic fallbacks rather than blocking fulfilment.
Two narratives are running in parallel. Carrier-side, Starshipit is deepening its cross-border story (importer-of-record settings, third-party duty billing, package-level commodity codes) and broadening its carrier roster, particularly in ANZ. Operations-side, the warehouse module signals a shift from 'we print your labels' to 'we run your fulfilment'. That's a meaningful re-positioning against pure-shipping competitors and against entry-level WMS vendors at once.
Expect the warehouse module to deepen toward features that historically gate WMS adoption — multi-warehouse routing, lot/serial tracking, returns processing — and continued cross-border carrier additions to back the shipping-side story.
Medusa is settling into a steady cadence of point releases while rebuilding its starter around a monorepo.
Medusa is in maintenance mode on the 2.14 line, shipping two patch releases (v2.14.1, v2.14.2) in the past three weeks alongside cleanup work on snapshot files. The headline change of the cycle was v2.14.0, which restructured create-medusa-app into a monorepo with separate backend and storefront packages. The project continues to draw broad contributor participation, with the v2.14.0 release crediting 15 contributors.
After a heavy second-half-2025 push that delivered experimental Translations, HMR for the backend, and priority-based event processing, the project has shifted from feature expansion to consolidation. Recent work is dominated by version bumps, regression fixes, and starter ergonomics rather than new capability surface. The monorepo starter is the signal that the team is now thinking about how teams adopt and structure Medusa, not just what it can do.
Expect another patch release on the 2.14 line within the next few weeks, then a 2.15 cut that builds on the new monorepo starter — most likely tighter storefront-backend conventions, or graduating Translations or HMR out of experimental.
See more alternatives to Starshipit →
See more alternatives to Medusa →