Medusa

Self-hosted Shopify alternative, honestly reviewed. No marketing fluff, just what you get when you deploy it.

TL;DR

• What it is: Open-source headless commerce platform built on Node.js and TypeScript — handles products, orders, customers, payments, shipping, and promotions via API, with no frontend opinions [3].
• Who it’s for: Developers building bespoke stores with complex requirements that Shopify’s template system can’t accommodate. Enterprise teams with custom workflows. B2B, marketplace, or multi-region setups where flexibility matters more than launch speed [3][4].
• Cost savings: No GMV tax, no platform transaction fees, no monthly SaaS charges. You pay for hosting and your payment processor — that’s it. For merchants doing serious volume, the delta versus Shopify Advanced ($399+/mo) compounds fast [3][website].
• Key strength: The most flexible open-source commerce backend available in the JavaScript ecosystem. Headless architecture lets you pair it with any frontend — Next.js, Astro, plain React — and the module system means customizing checkout, pricing logic, or inventory rules doesn’t require fighting the platform [3][4].
• Key weakness: This is unambiguously a developer’s tool. If you don’t have a developer, or can’t hire one, Medusa is not for you. The Reddit community has also raised legitimate questions about whether the GitHub star growth reflects real organic adoption or inflated metrics [5].

---

What is Medusa

Medusa is an open-source headless commerce platform. You get a backend server with REST APIs and a built-in framework for customizations, an admin dashboard, and a set of commerce modules (products, orders, inventory, pricing, promotions, shipping) that you compose and extend. What you don’t get is a storefront — you build that yourself [3][4].

The company’s own positioning says “A Commerce Platform for Developers and Agents,” and the “agents” part is recent — they’ve added an AI-powered commerce builder called Bloom, a Docs MCP server, and integrations with Claude for agentic development [website]. Whether that matters for most buyers is a separate question.

The homepage claims real traction: “#1 of 15,000 GitHub commerce projects,” “+14,000 community developers,” “+2,500,000 yearly downloads,” ”+$10B global GMV powered” [website]. Some of these numbers are plausible for a project that’s been around since ~2021. The GitHub star count has been a point of skepticism (more on that below).

The technology stack is Node.js and TypeScript throughout. The architecture separates the backend commerce engine from the storefront entirely. This headless approach means you can redesign the storefront without touching backend logic, swap payment providers without rebuilding the frontend, and connect Medusa to any system via its REST API [3].

---

Why people choose it

The comparison that comes up most in the reviews isn’t n8n versus Activepieces — it’s Medusa versus Shopify. And the case Medusa makes against Shopify is coherent, if developer-dependent.

The Shopify bill problem. Forty Miles West [3] articulates it plainly: “We have seen clients paying hundreds of pounds a month in combined Shopify and app fees before they have sold a single product.” Monthly platform fees stack whether or not you’re selling. Liquid templating fights you when you need something custom. Every extra feature requires an app, and many apps carry their own subscriptions. The transaction fee structure (unless you use Shopify Payments) eats margin at scale.

Full control over checkout. With Medusa, the checkout flow is yours. Multi-step checkout with custom validation, location-based payment options, subscription models alongside one-off purchases — none of this requires a third-party app [3]. For businesses with non-standard commerce flows — B2B pricing tiers, marketplace logic, complex bundles — this matters enormously.

No GMV tax, no platform fees. The website is explicit: “no GMV tax or licenses” [website]. For a merchant doing $4 million in annual sales, the difference between a 0.5% platform fee and zero is $20,000/year. Thoughtworks reportedly built a full B2B enterprise platform with 18 integrations powering $4bn in digital sales in six months using Medusa [website testimonial].

The developer community’s read. Product Hunt reviewers [2] describe it as “a strong fit for developers who want an open-source, self-hosted alternative to Shopify with deep customization and control over the stack.” Reviewers consistently praise the flexibility and headless approach. The one repeated caveat: it expects coding knowledge, and one user specifically calls out weak payment integrations — particularly PayPal — as an area that still needs work [2].

The GitHub star skepticism. The Reddit thread from r/selfhosted [5] is worth quoting directly: “The package had a very fast growth in popularity and yet no one talks about it, why?” The poster notes that despite reaching 20K GitHub stars (at the time), it was hard to find organic discussion — most posts looked like SEO-driven content, and it rarely appeared in authentic “what do you recommend for an online store” conversations. The star count beats PrestaShop, Sylius, and even outdid WordPress by 2,000 stars at the time. That’s suspicious growth for a project with limited organic forum presence. This doesn’t mean Medusa is a bad product — it means treating the GitHub star count as a proxy for community health is unreliable here [5].

---

Features

Based on the README and website:

Core commerce modules:

• Product management with bundles, variants, and a bulk editor [website]
• Multiple sales channels with different rules and products (multi-store, POS, apps) [website]
• Inventory and multi-warehousing with order reservations [website]
• Multi-regional by default: multiple currencies, local tax rules, region-specific shipping, payment, and discounts [website]
• Advanced promotion engine: campaigns, B2B pricing, free shipping rules, customer-specific pricing [website]

Checkout and orders:

• Full API-driven checkout — no black box, every step customizable [3]
• Return/RMA flows [4]
• Subscription support alongside one-off purchases without third-party apps [3]

Integrations:

• 100+ community integrations [website]
• Pre-built React starters for B2C, B2B, POS, and Marketplaces [website]
• Payment processor integrations (noted weakness: PayPal specifically called out as needing improvement) [2]
• Docker deployment on any infrastructure [1]

AI and developer tooling:

• Bloom: AI-powered commerce builder (“go from idea to online shop in a single prompt”) [website]
• Docs MCP server and AI Development Assistant [website]
• Claude integration for agentic development [website]
• REST API throughout [4][features]

Admin:

• Customizable admin dashboard [website]
• Separate from the storefront — can be customized independently [3]

---

Pricing: SaaS vs self-hosted math

Medusa’s pricing page exists but specific tier prices weren’t captured in the scraped data [website pricing]. What the website does state clearly:

Medusa Cloud:

• Linked to your own GitHub repository — you own the code [1]
• Pre-configured PostgreSQL, Redis, S3, email services — no manual infrastructure setup [1]
• Auto-scaling, high availability, preview environments, push-to-deploy [1]
• “No hidden fees — only pay for the infrastructure, no extra licenses or GMV tax” [website]
• Pricing: visit https://medusajs.com/pricing for current numbers — not included in scraped data

Self-hosted:

• Software: open source (MIT license based on articles; note: the merged profile listed GPL-3.0 which appears to be a data error from a different “Medusa” project) [3][4]
• Infrastructure: you choose — Railway, DigitalOcean, AWS, or any VPS
• Requires: PostgreSQL, Redis, file storage (S3-compatible), email service — all manual setup [1]

Shopify for comparison (from Shopify’s published pricing):

• Basic: $39/mo + transaction fees unless using Shopify Payments
• Shopify: $105/mo
• Advanced: $399/mo
• Plus (enterprise): $2,300/mo
• App fees on top of all tiers

The self-hosting math is compelling for any merchant doing real volume. A $20/mo VPS and managed PostgreSQL running a $500K/year store saves the platform percentage and the app stack. The catch is the engineering cost of deploying and maintaining it.

---

Deployment reality check

This is where the honest conversation about Medusa’s audience has to happen.

What the Medusa docs say about self-hosting [1]: The official documentation doesn’t soft-pedal the complexity. The self-hosting vs. cloud comparison table lists these self-hosting requirements: manual configuration of servers, databases, and other services; complex setup of deployment environment; manual setup of scaling policies; manual redundancy and failover; manual performance optimization; separate storefront deployment and configuration; manual email infrastructure setup; manual data backup setup.

That’s not a scare tactic — that’s an accurate description of what running a production commerce backend looks like.

What you actually need for a minimal self-hosted setup:

• A VPS (at least 2GB RAM; 4GB+ for production load)
• PostgreSQL (managed service or self-hosted)
• Redis
• S3-compatible file storage
• SMTP or transactional email service
• A domain, TLS certificate, reverse proxy
• Docker or manual Node.js deployment
• Someone who can debug when something breaks at 2am

Medusa Cloud vs. self-hosting: The docs make the case for Medusa Cloud clearly [1]: GitHub integration, push-to-deploy, preview environments, auto-scaling, built-in email, automated backups, dedicated support. If you don’t have infrastructure experience, Cloud is the honest recommendation even if it costs more.

Realistic time estimate: For an experienced developer familiar with Docker and cloud infrastructure, a working self-hosted instance takes a few hours. For someone new to backend deployment, a full working day minimum. For a non-technical founder without help — this is not a self-service tool.

---

Pros and Cons

Pros

• No platform fees or GMV tax. You pay infrastructure and payment processor. At volume, this matters significantly [3][website].
• Full checkout ownership. Every step of the purchase flow is yours to customize — no fighting a black box or paying for a checkout app [3].
• Headless architecture. Your frontend is completely decoupled. Rebuild the storefront, swap a payment provider, add a new sales channel — none of these require touching the others [3].
• Genuinely composable modules. Products, orders, inventory, pricing, promotions — each is a module you can extend or replace. This is not a “fork it and hack it” open source project; the extension model is intentional [4][website].
• Multi-region built-in. Multiple currencies, local tax rules, regional shipping — without third-party plugins [website].
• B2B and marketplace support. Complex buying flows that would require expensive Shopify Plus apps are first-class features here [3][website].
• Own your data. Customer records, order history, product data — lives in your database, under your terms [3].

Cons

• Developer required. This is not a “launch by Friday” tool for a non-technical founder. Every source agrees on this. Product Hunt reviewers specifically flag it requires coding knowledge [2][3][5].
• Weak payment integrations in places. PayPal specifically flagged as undercooked [2]. If your customers expect PayPal and it doesn’t work reliably, that’s a conversion problem.
• No storefront included. You build it. Pre-built React starters exist and help, but they’re a starting point, not a production-ready storefront [website].
• GitHub star credibility questions. The growth pattern looks unusual relative to organic community discussion. Stars may not reflect real adoption numbers as accurately as they do for other tools [5].
• Self-hosting complexity is real. The official docs describe 10+ manual setup concerns for production deployment [1]. This isn’t a one-click install.
• Smaller community than Shopify’s ecosystem. 100+ community integrations [website] versus Shopify’s thousands of apps. Long-tail SaaS integrations often aren’t there.
• The “AI-first” framing oversells the product for most buyers. Bloom and the MCP server are interesting features for developers, but most merchants need reliable checkout and inventory management, not agentic development tooling.

---

Who should use this / who shouldn’t

Use Medusa if:

• You have a developer (in-house or contracted) who will own the deployment and maintenance.
• Your commerce requirements genuinely can’t be met by Shopify — complex B2B pricing, marketplace flows, subscription models, heavy regional customization.
• You’re paying $399+/mo on Shopify Advanced and the platform transaction fees or app stack is eating margin.
• You want to own your customer data and commerce logic without platform lock-in.
• You’re building a custom commerce product for clients (agency use case — Forty Miles West specifically makes this case [3]).

Skip it (stay on Shopify) if:

• You’re a non-technical founder launching a straightforward retail store and need to be live quickly.
• You don’t have developer resources and won’t hire them.
• Your product catalog and checkout flow are standard — Shopify’s templates and app ecosystem will handle it cheaper in engineer-time.
• Your volume is low enough that platform fees aren’t painful yet.

Skip it (consider WooCommerce) if:

• You’re already in the WordPress ecosystem and your commerce needs are relatively simple [3].

Skip it (consider Sylius) if:

• Your team works in PHP/Symfony and you prefer that stack to Node.js/TypeScript [4].

---

Alternatives worth considering

• Shopify — the incumbent. Fastest launch, largest app ecosystem, built-in payment processing. Monthly fees and transaction charges scale with your revenue. Fully closed source [3].
• WooCommerce — WordPress-native, good if you’re already in that ecosystem. Less suited to headless or complex custom flows [3].
• Sylius — PHP/Symfony-based headless commerce. Similar flexibility philosophy, different language ecosystem. About 7,000+ GitHub stars; stronger in enterprise PHP shops [4].
• PrestaShop — older PHP platform, larger plugin ecosystem than Sylius but more legacy architecture [5].
• Saleor — Python/Django-based headless commerce. Similar positioning to Medusa, different language stack. Worth comparing if you have Python expertise.
• Vendure — TypeScript/Node.js like Medusa, GraphQL-first API. More opinionated but with strong typing throughout.

For a non-technical founder escaping Shopify bills: Medusa is not the right direct answer. For a developer or agency building a client’s custom commerce system: Medusa is one of the more credible options in the JavaScript ecosystem right now.

---

Bottom line

Medusa is a serious, genuinely flexible commerce backend for developers who need to build something that doesn’t fit inside Shopify’s model. The no-GMV-tax, no-platform-fee proposition is real, the headless architecture is legitimate, and the module system means extending it doesn’t require forking the core. The trade-off is unambiguous: you need engineering resources to deploy, customize, and maintain it. The Reddit community’s skepticism about the GitHub star growth is worth holding in mind when evaluating its apparent popularity [5] — the organic forum presence doesn’t match the star count, and the quality of third-party reviews is uneven. None of that means the product is bad; it means verify it fits your situation before committing. If you have a developer and a commerce problem that Shopify keeps charging you $50 app subscriptions to half-solve, Medusa is worth a serious evaluation. If you’re a non-technical founder looking for a self-hosted Shopify alternative you can deploy yourself, look elsewhere.

---

Sources

1. Medusa Docs — Cloud vs Self-Hosting (official documentation comparing deployment options). https://docs.medusajs.com/cloud/comparison
2. Product Hunt — Medusa Reviews (10 reviews, 4.4/5 aggregate). https://www.producthunt.com/products/medusa/reviews
3. Forty Miles West — “Medusa.js: The Open-Source Alternative to Shopify” (agency perspective, Shopify vs Medusa comparison). https://fortymileswest.co.uk/blog/medusa-js-open-source-ecommerce/
4. Edna Ololade, Medium — “Medusa Vs. Sylius: Which Should You Use for Your Ecommerce?” (Mar 2023, feature-by-feature comparison). https://medium.com/@ednaololade/medusa-vs-sylius-which-should-you-use-for-your-ecommerce-500bb1d573e3
5. r/selfhosted — “Do you know Medusa.js? What’s your experience with it?” (community thread questioning GitHub star growth and organic adoption). https://www.reddit.com/r/selfhosted/comments/1849677/do_you_know_medusajs_whats_your_experience_with_it/

Primary sources:

• Official website: https://medusajs.com
• Pricing page: https://medusajs.com/pricing
• GitHub repository: https://github.com/medusajs/medusa