Medusa on Railway
Medusa v2 commerce backend, admin, worker, Next.js storefront and search on Railway.
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
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
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.