Medusa.js Pricing: Cloud Plans, Self-Hosting Costs, and What You Actually Pay

Medusa.js is MIT-licensed open source software, so the framework itself is free. What you pay for is hosting, infrastructure usage, and developer time. As of April 2026, Medusa Cloud's public plans are Develop from $29/month, Launch from $99/month, Scale from $299/month, and Enterprise with custom pricing. Medusa also publishes usage-based add-ons and overages for items such as preview environments, compute hours, data transfer, storage, build minutes, emails, and extra Cloud seats — so the real bill can be higher than the base plan price depending on how you deploy and scale.

Reviewed: April 2026 | Covers Medusa.js v2 and Medusa Cloud current pricing. Pricing noted here reflects official public plan pages as of this review date. Pricing varies by region, contract term, usage, and payment gateway — always verify with the vendor before making a purchasing decision.

Methodology note: Cloud plan prices in this article are taken from Medusa's official pricing page. Self-hosting cost examples are modeled estimates based on current public provider pricing — they are labeled as such throughout.

About the author: I'm Matija, an independent developer specialising in Next.js, Payload CMS, and headless commerce architectures. I've shipped multiple Medusa implementations including backend setup, storefront builds, and payment integration — both self-hosted and on managed infrastructure. The self-hosting cost models and operational notes in this article come from those builds.

---

The Three Cost Models

When someone asks "how much does Medusa.js cost," they are usually conflating three separate questions. The platform license is free. The running infrastructure is not. And the developer time to build a production Medusa store is a real number that most pricing articles skip entirely.

Here is how to think about the three models before diving into the specifics.

---

Medusa Cloud Pricing

Medusa Cloud is the managed hosting service — you deploy your Medusa instance there and Medusa handles the underlying infrastructure. As of April 2026, the public plan structure is:

A few plan-specific details matter for accurate budgeting. Preview environments are available across all plans. Autoscaling, automatic backups, and zero-downtime deployment start at Launch — the Develop plan does not include those features. Beyond the base monthly fee, Medusa publishes usage-based add-ons and overages for compute hours, data transfer, object storage, database storage, build minutes, emails, and extra Cloud seats. The real monthly bill can therefore run higher than the base plan price depending on how you build and scale.

Medusa's pricing documentation also publishes the infrastructure shape by plan and included quotas, which is worth knowing before you commit. Develop runs on one shared server. Launch runs on two shared servers with autoscaling. Scale adds a dedicated worker instance on top of the two servers with autoscaling. On included quotas across Develop, Launch, and Scale: preview environments are 1, 3, and 5 respectively; monthly build minutes are 300, 500, and 1,000; Cloud seats are 1, 1, and 3; and monthly email limits are 1,000, 10,000, and 25,000. Compute hours, data transfer, storage, and database storage have separate included allocations with overage rates published in the docs.

The most important structural fact: Medusa Cloud charges no GMV-based transaction fees on any plan. You pay for infrastructure, not a percentage of revenue. That is the key difference from Shopify's third-party transaction fee model.

---

Self-Hosting Cost Breakdown

Self-hosting Medusa means you run the platform on your own infrastructure. The software is free. The hosting is not.

Official production requirements. Medusa's deployment documentation specifies that a self-hosted production instance requires PostgreSQL, Redis, and S3-compatible object storage for file handling. Medusa's general deployment guide also recommends running two separate Medusa instances: one server process and one worker process. Most self-hosting cost estimates — including earlier versions of this article — price only a single Node.js server and therefore understate real production complexity.

The following table shows two modeled cost scenarios using current public provider pricing. These are estimates, not official Medusa figures.

Prices reflect Render and DigitalOcean public plan pricing as of April 2026. These are modeled estimates, not official Medusa figures.

The lean starter runs tight — Render Starter instances have limited memory and are not suited to stores with heavy traffic. The comfortable starter gives you room to breathe and is more representative of a real production workload. At higher scale, move to larger instance sizes or AWS/GCP equivalents, and costs grow accordingly.

The honest operational caveat: self-hosting requires DevOps capacity. For teams without a dedicated infrastructure person, the engineering time spent on deployment, monitoring, updates, and incident response often exceeds the cost difference between self-hosting and Medusa Cloud. The $99/mo Launch plan in particular is easy to justify once you factor in the hours saved on infrastructure management.

---

The Developer Cost That Nobody Talks About

Medusa is not a plug-and-play platform. It is a composable commerce framework — powerful, flexible, and designed for developers who want full control over the stack. That strength means every production Medusa implementation requires real developer time.

A basic Medusa backend with a Next.js storefront is a meaningful engagement. You are setting up the Medusa server, configuring modules for payments, shipping, and email, building or adapting the storefront, connecting to your CDN and storage, and testing the full checkout flow. A capable developer working full-time takes days to weeks, not hours.

This cost exists whether you are building it yourself or hiring an agency. It is the most important number to factor into a Medusa cost analysis, and it is consistently absent from pricing pages and overview articles.

---

Medusa Cloud vs Self-Hosting: Decision Framework

The decision between managed Cloud and self-hosted infrastructure comes down to your team's infrastructure capability, your timeline, and your compliance requirements.

Choose Medusa Cloud when:

You want to ship fast without managing infrastructure. Your team does not have dedicated DevOps capacity. The $29–$299/mo monthly base cost is lower than the engineer-hours required to run and maintain your own setup. You are planning to go live and need autoscaling, automatic backups, and zero-downtime deploys — those features start at the Launch plan ($99/mo).

Choose self-hosting when:

You have existing infrastructure and DevOps tooling already in place. You need infrastructure, residency, or compliance controls that require hosting on your own stack. You want maximum control and the lowest possible monthly bill at scale. Docker combined with Railway or Render is already part of your stack — in which case the operational overhead is minimal because you are already working in that environment.

---

How Medusa Pricing Compares to the Alternatives

The numbers that make the decision concrete. Medusa Cloud figures are from Medusa's official pricing page as of April 2026. Shopify figures use US monthly pricing on a one-year billing term — Shopify pricing is localised by country and varies by billing term and contract structure, so check Shopify's regional pricing page for your market.

US monthly price, one-year term. Shopify pricing varies by region and billing cycle. †Shopify Plus standard plans have fixed monthly pricing. For higher-volume, more complex businesses, Shopify Plus can move to a variable platform fee based on revenue and business model. "None" applies to standard setups only.

Note on Saleor: Saleor has a published pricing page but I was unable to verify current plan amounts from a primary source at time of writing. I have removed that row rather than publish unverifiable figures.

The Shopify transaction fee qualifier. Shopify subscription pricing and payment rates vary by country, billing term, and contract structure. On standard plans, Shopify charges extra transaction fees when you use a third-party payment provider — but those fees are generally waived for payments processed through Shopify Payments, Shop Pay, Shop Pay Installments, PayPal Express, and manual payment methods. There are edge cases for store credit and gift cards on some stores created on or after May 12, 2025, and Shopify Plus pricing can move to a variable platform fee for more complex, higher-volume setups. Always check Shopify's current regional pricing and help documentation before using a fixed comparison figure.

With that qualifier in place, here is how the math looks as a scenario. A store processing $500,000 GMV per year on Shopify Basic using a third-party processor pays $10,000 per year in transaction fees alone. Medusa Cloud Scale at $299/mo is $3,588 per year with zero platform transaction fees. The transaction-fee-only crossover against the Scale plan is around $179,400 GMV per year. Against Launch ($99/mo, $1,188/yr), the crossover is around $59,400 GMV. Against Develop ($29/mo, $348/yr), it is around $17,400 GMV.

These crossover calculations cover transaction fees only. They exclude payment processing fees (which both platforms pay), developer time, app costs, and any Medusa Cloud usage overages. Treat them as directional guidance, not a complete TCO comparison.

---

Hidden Costs to Factor In

A complete Medusa cost analysis includes a few line items that are easy to miss upfront.

Storefront build. Medusa has no built-in storefront. You build one with Next.js, use the official Next.js starter as a base, or use another framework. That is developer time on top of the backend setup.

Admin customisation. The Medusa Admin is solid out of the box. Custom admin views, bulk operations, or workflow-specific tooling require development work.

Integrations. Payment providers, shipping carriers, email services, and ERP connections each need configuration. Some have official Medusa plugins with good documentation. Others need custom implementation. Budget time per integration, not just per provider category.

Ongoing maintenance. Updates, security patches, and dependency management are a recurring cost. The overhead is lower than maintaining a WooCommerce plugin stack, but it is not zero. Self-hosters carry more of this burden than Medusa Cloud users.

---

Frequently Asked Questions

Is Medusa.js really free? The platform is MIT-licensed and free to use. You pay for hosting and developer time — not the software itself.

Does Medusa charge transaction fees? No. There are no GMV-based platform fees on any Medusa Cloud plan. You pay a base monthly fee plus any usage-based overages for compute, storage, and other resources.

What is the cheapest way to run Medusa in production? Self-hosted on Render with a managed PostgreSQL instance. A lean two-process setup (server + worker) runs around $35/mo using current Render public pricing. You need to be comfortable managing deployment, updates, and monitoring yourself.

Is Medusa Cloud worth it vs self-hosting? For most teams without dedicated DevOps capacity, yes. The Launch plan at $99/mo includes autoscaling, automatic backups, and zero-downtime deploys — features you would otherwise need to build and maintain yourself. For teams already running Docker-based infrastructure on Railway or Render, self-hosting is a reasonable path with lower monthly costs.

How does Medusa pricing compare to Shopify at scale? The comparison depends on your payment setup. If you use a third-party processor on Shopify, transaction fees scale with revenue. Medusa charges no GMV-based fees. The transaction-fee crossover against Medusa's Scale plan ($299/mo) occurs at around $179,400 GMV per year using Shopify Basic's current 2% third-party rate. If you use Shopify Payments, those transaction fees are waived and the comparison shifts back toward total infrastructure cost.

What does a complete Medusa implementation cost including development? This varies widely. A basic backend with a Next.js storefront from a capable developer or agency is a significant engagement. Plan for weeks of development time, not hours. Ongoing maintenance is an additional recurring cost.

---

Summary

Medusa.js is free software with real infrastructure and developer costs attached to it. The platform license costs nothing. As of April 2026, Medusa Cloud plans run $29/mo (Develop), $99/mo (Launch), and $299/mo (Scale), with usage-based overages on top depending on compute, storage, and other resources. Self-hosting runs roughly $35–$106/mo for a lean two-process setup on managed providers, with costs growing from there at scale. Developer time to build a production store is the largest cost for most teams and the one most pricing articles ignore.

If you are evaluating Medusa for a client project or your own store and want help with the build, get in touch — I work with Medusa and Next.js regularly. And if you are comparing Medusa against other platforms, the Medusa vs Shopify breakdown goes deeper on the technical and commercial tradeoffs.

Let me know in the comments if you have questions, and subscribe for more practical guides on Medusa, Payload CMS, and modern commerce architecture.

Thanks,Matija