Deploy and Host Medusa 1.x E-commerce (Legacy, unmaintained) on Railway

This template is no longer maintained. It deploys Medusa 1.x, which has been replaced by Medusa 2.0. Dependencies were last updated 21 June 2024 and it receives no fixes or updates. It stays published so existing stores and inbound links keep working.

👉 New project? Use the maintained Medusa 2.0 template instead: Medusa 2.0 + Next.js Storefront

It deploys a Medusa 2.0 backend, Next.js storefront, Postgres, Redis, MeiliSearch and S3-compatible object storage in one click, and it is actively kept up to date. Step by step guide and video: funkyton.com

An independent, community-maintained template by FUNKYTON. Not affiliated with, endorsed by, or supported by MedusaJS, Inc. or Railway. "Medusa" is a trademark of MedusaJS, Inc., used here only to describe what this template deploys.

About Hosting Medusa 1.x E-commerce (Legacy, unmaintained)

This is the original Medusa 1.x boilerplate: an all-in-one e-commerce stack with backend, admin dashboard and a connected storefront, wired to Postgres and Redis. Railway hosts all of it in one project.

Because Medusa 1.x is superseded, nothing here is being updated. Deploy it only if you specifically need version 1. For anything new, use the Medusa 2.0 template.

Already running this one? Your store keeps working. When you are ready to move, deploy the 2.0 template alongside it and migrate your data, rather than upgrading in place.

Original v1 setup guide and video: funkyton.com

Common Use Cases

Keeping an existing Medusa 1.x store running
Referencing the v1 setup while planning a migration to Medusa 2.0
Studying a complete v1 backend, admin and storefront wiring

For any new store, use the Medusa 2.0 template.

Dependencies for Medusa 1.x E-commerce Hosting

GitHub account and Railway account
Railway Hobby plan for ongoing use

Deployment Dependencies

Medusa 2.0 template, the maintained replacement for this one
Medusa v1 documentation, for anything about Medusa itself
Template repository and issues, for anything about this template or its Railway setup

Questions about this template belong in the repository issues above, not in Medusa's own support channels.

Why Deploy Medusa 1.x E-commerce on Railway?

Railway is a single platform for your whole infrastructure stack. It hosts your services so you do not have to deal with configuration, and lets you scale them vertically and horizontally.

For a new store, deploy the maintained Medusa 2.0 template, not this one.