Medusa on Railway

Medusa v2 commerce backend, admin, worker, Next.js storefront and search on Railway.

Official site · License: MIT · 21 Railway templates

Deploy Medusa on RailwayCompare templates

Medusa is an open-source commerce platform built on Node.js. It provides a modular backend with Store and Admin APIs, an admin dashboard, and workflows for products, carts, orders and payments. It is often compared with Shopify and with other headless options such as Saleor and Vendure, with the difference that you host and customise the backend yourself.

Developers use it to build custom storefronts and marketplaces where the backend logic needs to be changed in code. The official dtc-starter provides a Next.js storefront to start from.

Medusa and the starter are MIT-licensed; Medusa also sells Enterprise Edition materials separately.

What Medusa can do

  • Store and Admin APIs with an admin dashboard
  • Modular architecture with workflows, subscribers and scheduled jobs
  • Next.js storefront starter
  • Product, cart, order and region management
  • Payment and file providers through modules
  • Meilisearch product search through a plugin

What people use it for

  • A custom online store with a Next.js storefront
  • A headless commerce backend for an existing frontend
  • Marketplaces and B2B stores with custom logic
  • Replacing a hosted store platform you outgrew

Videos

Medusa.js in 90 seconds · Nick Vogel
E-commerce Website with Medusa + Next.js : A Beginner's Guide · The Full Stack Junkie
I Built the Same Store with Medusa, Vendure & Saleor (Which is Best?) · Raj Mahil | 306 Technologies

Running Medusa on Railway

On Railway, the Medusa template deploys the backend with the admin at /app, a separate worker for subscribers, jobs and search indexing, the dtc-starter Next.js storefront, Meilisearch, Postgres 18, Redis 8.2 and a private Railway Bucket for product images served through a read-only media proxy. Migrations run before deploy with demo products. Railway bills the CPU and memory used across the seven services plus bucket storage.

Medusa templates on Railway

Medusa v2 Commerce Store (Backend + Storefront)Maintained by Tracklayer
Deploys a Medusa 2.21 store: backend with admin dashboard, background worker, the Next.js 15 storefront from the official dtc-starter, Meilisearch search, Postgres, Redis and a Rai
4 deployments
Deploy
Medusajs 2.0 + Next.js Storefront by Rasmus Puls's Projects
Full ecommerce solution, manage products, inventory, orders, etc.
3,249 deployments
Deploy
(v1) Medusa Backend with Worker Modes by Shahed Nasser's Projects
Deploy an ecommerce backend and admin using Medusa
1,994 deployments
Deploy
medusajs ecommerce Nextjs, Postgres, Redis by Rasmus Puls's Projects
Full ecommerce solution, manage products, inventory, orders, etc.
1,036 deployments
Deploy
Medusajs 2.0 + Storefront (TRIAL) by Rasmus Puls's Projects
Full ecommerce solution, manage products, inventory, orders, etc.
543 deployments
Deploy
(v1) Simple Medusa Backend by an independent creator
Deploy an ecommerce backend and admin using Medusa
349 deployments
Deploy
Medusa.js v2 | Shopify Alternative by an independent creator
Self Host Medusajs v2: Headless Commerce with REST API, admin, workflows
130 deployments
Deploy
Medusajs 2.0 + Storefront (⚠️ DISCONTINUED) by an independent creator
Use instead: https://railway.com/deploy/medusajs-2-0-storefront
118 deployments
Deploy
Medusajs 2.0 + Storefront (B2B) by an independent creator
Fork of the official Medusajs V2 B2B starter, tweaked for Railway
72 deployments
Deploy
MedusaJS + Storefront (Railway Bucket) by an independent creator
MedusaJS + Storefront + Railway Bucket (Optimized for low-cost)
50 deployments
Deploy
Medusa.js by an independent creator
Open-source commerce backend for building your own online store
11 deployments
Deploy
Medusa.js | Shopify Alternative by an independent creator
Self-host Medusa.js v2. Zero transaction fees. Own your store data.
10 deployments
Deploy
Medusa by an independent creator
Medusa 2.20: server + worker, Postgres, Redis. Admin user created on boot.
4 deployments
Deploy
medusa-v2 by an independent creator
Medusa v2 commerce backend: server+worker split, Postgres+Redis, one-click
3 deployments
Deploy
Medusa by an independent creator
MedusaJS 2 commerce with admin and Next.js storefront, Postgres and Redis
2 deployments
Deploy
Medusa v2 (Worker Mode) by an independent creator
Medusa v2 with a dedicated background-job worker, search and storefront.
2 deployments
Deploy
medusa-store by an independent creator
Deploy Medusa Worker and Server with a private connection to Redis.
2 deployments
Deploy
Medusa by an independent creator
Medusa v2 commerce: admin, worker, Next.js storefront, Postgres, Redis
0 deployments
Deploy
Medusa 2 + Enthusiast Commerce by an independent creator
Medusa 2 commerce starter with Next.js, Shopping feeds and Enthusiast AI.
0 deployments
Deploy
Medusa 2 | (Just Updated) Headless Commerce API + Admin, 3 Services Not 6 by an independent creator
Commerce API + Admin, prebuilt: 3 services, migrations on every deploy.
0 deployments
Deploy
Medusa 2 | Migrations Before Traffic, Admin on First Boot by an independent creator
Medusa 2 pinned. Migrations before traffic, admin created on first boot.
0 deployments
Deploy

Tracklayer templates are listed first. Other Medusa templates follow, ordered by total deployments on Railway. How this works.

Deployment numbers as of 2026-11-20.

Questions about Medusa

How do I log in to the admin?

Set MEDUSA_ADMIN_EMAIL on the backend before deploying (default admin@example.com). When the services are healthy, open the backend domain at /app and sign in with that email and the generated MEDUSA_ADMIN_PASSWORD from the Variables tab.

How do I take payments?

Payments are not live by default. Add STRIPE_API_KEY and STRIPE_WEBHOOK_SECRET on the backend and NEXT_PUBLIC_STRIPE_KEY on the storefront when you are ready.

What drives the cost?

Seven services run: backend, worker, storefront, media proxy, Meilisearch, Postgres and Redis, plus bucket storage. The template notes recommend the Hobby plan or higher.

What persists, and how do I upgrade?

Postgres, Redis and Meilisearch use volumes and uploads sit in the Bucket. The starter commit and plugin version are build arguments in the Dockerfiles; change them together and redeploy.

Any licence notes?

Medusa, the starter and Meilisearch Community are MIT. Medusa Enterprise Edition materials and Meilisearch Enterprise parts are not used. Redis 8 is RSALv2, SSPLv1 or AGPLv3.

Guides

Similar apps

Tracklayer maintains the templates marked as such; Medusa is a trademark of its owners and this site is not affiliated with them.