Reaction Commerce on VPS: Installing the Node.js GraphQL Platform, Its Honest History, and Live Alternatives

31.03.2026

17:05

Reaction Commerce is a name worth knowing even if you'll never deploy it. The platform set the standard for API-first e-commerce on Node.js long before that was mainstream: GraphQL, MongoDB, modular architecture, Docker-based deployment — all of this appeared in Reaction as early as 2015–2016, when most shops were still running PHP monoliths.

First, the honest part: the project is officially discontinued. Mailchimp acquired Reaction Commerce in 2020, renamed it Mailchimp Open Commerce, then froze development. The GitHub repository has carried the label "Project has been discontinued" since 2024. The last meaningful commit was August 2025.

That doesn't mean the code doesn't work — it does. But building a new store on it in 2026 is a deliberate decision made with open eyes, not an accidental choice.

Below is the full picture: what Reaction Commerce is, how to install it, and what to choose instead if you need a living platform.

What Is Reaction Commerce (Mailchimp Open Commerce)

Reaction Commerce was founded in 2015 in Santa Monica, California. The concept: a next-generation e-commerce platform, fully API-first, without a monolithic frontend. In April 2020, Mailchimp acquired the company — founder Sara Hicks joined Mailchimp as VP Product. Mailchimp renamed the product Open Commerce and supported it as open source for several years. Then stopped.

Technical stack:

Node.js + jаvascript (not TypeScript, unlike Medusa or Vendure)
MongoDB — primary database; replica set required in production
GraphQL via Apollo Server — the only API, no REST
Hydra (OAuth2/OIDC) — authentication layer, requires PostgreSQL
Docker and Docker Compose — the recommended deployment method
React + Next.js — the reference Example Storefront

Three separate components:

The API server listens on port 3000 and exposes all GraphQL endpoints. The Admin panel on port 4080 is a standalone React application. The Example Storefront on port 4000 is a Next.js reference storefront connecting to the API. Each component lives in its own repository and runs in its own Docker container.

License: GPLv3 — more restrictive than the MIT license used by Medusa. Derivative products must also be open source.

Should You Install Reaction Commerce in 2026

The honest answer is no, for a new project. Here's why:

The community is gone. New bugs don't get fixed. Dependencies are aging. MongoDB changed its licensing terms. Node.js keeps moving forward and compatibility with older versions goes untested.

There are scenarios where it makes sense: you already run Reaction Commerce in production and want to update your infrastructure without touching the application code; or you're studying API-first e-commerce architecture and want to run a reference implementation to understand the patterns.

For a new project, look at the live platforms listed below.

Installing on VPS with Docker

If you've decided to install anyway, here's the working method. Docker Compose is the only officially supported deployment approach.

VPS Preparation

Minimum: 2 GB RAM per container (API + Mongo + Admin + Storefront on one VPS requires 4 GB+). Standard VPS with 4 vCPU / 8 GB RAM / NVMe on THE.Hosting is the recommended starting point.

Connect:

ssh root@your-IP-address
apt update && apt upgrade -y

Installing Docker and Docker Compose

curl -fsSL https://get.docker.com | sh
systemctl start docker
systemctl enable docker
apt install docker-compose-plugin -y
docker --version
docker compose version

Cloning and Configuration

git clone https://github.com/reactioncommerce/reaction-development-platform.git
cd reaction-development-platform

The directory contains a Makefile that clones all three repositories (API, Admin, Storefront) and orchestrates them via Docker Compose.

Critical for VPS deployment (not localhost): several configuration files hardcode http://localhost. Before running, replace these with your server's IP address or domain. The specific files are listed in the repository's README.md.

Run:

make

This clones the repositories, pulls Docker images, applies configuration, and starts all containers. From scratch — 10–20 minutes depending on your connection speed.

Once running:

Component	URL
GraphQL API + Playground	http://your-IP:3000/graphql
Admin Dashboard	http://your-IP:4080
Example Storefront	http://your-IP:4000

Production MongoDB Requirements

In production, MongoDB must run as a replica set with oplog enabled — the platform uses change streams. A standalone MongoDB instance without replication doesn't support change streams and several platform features will break silently.

For a proper production deployment:

# In the API server's .env file
MONGO_URL=mongodb://user:pass@host:27017/reaction?replicaSet=rs0&authSource=admin
MONGO_OPLOG_URL=mongodb://user:pass@host:27017/local?replicaSet=rs0&authSource=admin

Nginx and SSL

apt install nginx certbot python3-certbot-nginx -y

Configure virtual hosts proxying requests to ports 3000, 4080, and 4000 based on domain or subdomain. Certbot adds HTTPS automatically.

Live Node.js Alternatives

If you need an actively developed platform with the same API-first approach, here's what actually works in 2026 — both documented with full installation guides on THE.Hosting.

Medusa — Open-Source Shopify Alternative

Stack: Node.js, TypeScript, PostgreSQL, Redis, REST API (GraphQL optional)
License: MIT
GitHub: 20,000+ stars, active daily commits
Similarities to Reaction: API-first, separate frontend, VPS-friendly
Improvements: active development, PostgreSQL instead of MongoDB, official Next.js Storefront, no abandoned dependency problem
Differences: REST API instead of GraphQL (for many this is a plus), no Hydra/OAuth2 layer to manage

Medusa is widely seen as the direct successor to Reaction Commerce's ideas — rewritten on a modern stack.

Installing Medusa on VPS — step-by-step guide

Vendure — GraphQL Framework on NestJS

Stack: Node.js, TypeScript, NestJS, GraphQL (Apollo), PostgreSQL, Redis
License: GPLv3 (same as Reaction) + commercial
GitHub: active development
Similarities to Reaction: GraphQL API, API-first, plugin-based modular architecture
Improvements: full TypeScript codebase, NestJS patterns, PostgreSQL, active community
For whom: developers who specifically want GraphQL as in Reaction Commerce, but on a living maintained platform

If GraphQL matters to you, Vendure is the direct Reaction Commerce replacement with a modern TypeScript stack.

Installing Vendure on VPS — step-by-step guide

Choosing a VPS

All three platforms (Reaction, Medusa, Vendure) need at least 4 GB RAM for comfortable production operation — the Node.js process, database, and cache all run simultaneously.

THE.Hosting has a starting VPS plan from €5.77/mo — suitable for testing and smaller stores with moderate traffic. For production, Standard VPS with 4–8 GB RAM is recommended.

Separately: after completing KYC (identity verification), a trial VPS at €1/mo is available — maximum rental period of 6 months. A good fit for deploying and evaluating any of these platforms before committing.

Location depends on your audience. For European stores — Germany (Frankfurt) or Netherlands (Meppel). For the North American market — USA (New Jersey). For Asian audiences — Japan (Tokyo) or Hong Kong. For CIS — Moldova (Chișinău) or Finland (Helsinki).

VPS in 50+ locations — all plans

FAQ:

Does Reaction Commerce actually work? Technically yes — the code on GitHub is available, Docker images build, and the make installation completes. But there's been no active development since 2024, bugs aren't fixed, and dependencies keep aging.

How does Reaction Commerce differ from Medusa and Vendure? Reaction uses MongoDB and GraphQL, jаvascript without TypeScript. Medusa — PostgreSQL, REST API, TypeScript, actively developed. Vendure — PostgreSQL, GraphQL, TypeScript, NestJS. Both are alive; Reaction is not.

Why MongoDB and not PostgreSQL? Historically Reaction Commerce was designed around a document-oriented database for flexible product schemas. MongoDB seemed like the right choice for e-commerce at the time. Modern platforms (Medusa, Vendure, Saleor) moved to PostgreSQL — more predictable performance and ACID transactions.

Can I migrate from Reaction Commerce to Medusa? There's no automated migration tool, but the architecture is conceptually similar. The work involves: moving data from MongoDB to PostgreSQL (via a script or ETL process) and rewriting custom plugins for the new API. For a large store this is a significant project.

Useful Links:

Reaction Commerce / Open Commerce Resources:

Order a new VPS in Bosnia with a 75% discount!

A reliable server for your projects at an affordable price.

Choose a VPS