Deploy and Host Medusa 2 + Enthusiast Commerce

A reusable production starter for a branded Dutch/Belgian webshop. It combines a Medusa 2 backend, a conversion-focused Next.js storefront and the complete Enthusiast AI stack.

About Hosting

This template deploys the complete commerce stack to Railway. Medusa and Enthusiast each receive an isolated PostgreSQL database and Redis instance. The public storefront, Medusa API/Admin and Enthusiast interface receive their own service and health check. Internal service references and generated secrets are configured automatically.

Why Deploy

Use this template when you want a repeatable webshop foundation without rebuilding hosting, databases, feeds, inventory controls and Enthusiast integration for every new brand. The services are separated so they can scale, restart and be maintained independently.

Common Use Cases

• Launch a new branded Medusa 2 webshop for the Netherlands or Belgium.
• Reuse the LVRO-style commerce workflow without copying production data.
• Manage products, inventory, sourcing costs and Shopping approval in one backend.
• Add Enthusiast AI with separate API, worker, scheduler and frontend services.
• Prepare Google Shopping, Meta and JSON feeds behind quality gates.

Dependencies for Medusa 2 + Enthusiast Commerce

The template uses public, versioned container images built from this repository. A fresh deployment does not require a separate GitHub App connection or local build environment.

Deployment Dependencies

• Railway account with capacity for ten services and four persistent volumes.
• PostgreSQL and Redis services included by the template.
• A Medusa publishable API key created after the first backend boot.
• Public backend and storefront domains for CORS configuration.
• Payment, email and analytics credentials only when those integrations are enabled.

Included

• Medusa 2 backend and admin
• Next.js storefront with mobile cart, checkout, account pages and service pages
• Google Shopping, Meta and JSON feeds
• SEO, structured data and Consent Mode-ready analytics
• Internal sourcing, margins, inventory and Shopping approval controls
• @upsidelab/medusa-plugin-enthusiast
• Enthusiast API, worker, scheduler and frontend
• PostgreSQL and Redis for both Medusa and Enthusiast
• Railway health checks and Docker builds
• Rebrand and template verification scripts

No LVRO production database, customer information, supplier catalog, scraped reviews or credentials are included.

One-click Railway deployment

Use the button to create a fresh stack. See docs/RAILWAY_TEMPLATE.md for the service map, required variables and first-deploy checklist.

Local development

Requirements: Node.js 20+, npm 10+, PostgreSQL and Redis.

npm install
cp apps/backend/.env.template apps/backend/.env
cp apps/storefront/.env.example apps/storefront/.env.local
npm run backend:dev
npm run storefront:dev

The backend uses port 9000 by default and the storefront uses port 8100.

Create a new brand

Run the rebrand command immediately after creating a repository from this template:

npm run rebrand -- \
  --name "My Store" \
  --domain "mystore.nl" \
  --email "service@mystore.nl" \
  --slug "mystore"

Then review the legal pages, contact details, shipping promise and payment provider configuration before launch. Legal text is a starting point and not legal advice.

First Medusa setup

1. Deploy the backend and let the migration/initial seed finish.
2. Open /app on the Medusa domain and create the owner account.
3. Copy the generated publishable API key to NEXT_PUBLIC_MEDUSA_PUBLISHABLE_KEY on the storefront service.
4. Set the backend and storefront public domains in the CORS variables.
5. Configure payments, shipping and transactional email.
6. Keep Shopping core feed mode disabled until product, stock and Merchant Center checks pass.

Safety defaults

• Unknown inventory is never invented.
• Shopping core-feed publication requires explicit approval.
• Sourcing data stays behind Medusa admin authorization.
• Analytics consent starts denied until the visitor opts in.
• Advertising campaigns are not activated by this repository.

License

The commerce starter is MIT licensed. Enthusiast is included under its upstream MIT license; see services/enthusiast/LICENSE.md.