Open-source, API-first commerce. The Node.js platform acquired by Mailchimp, now community-maintained.
Starts at Free (open source, Apache 2.0) · Best for developers wanting event-driven commerce, microservice architectures, legacy reaction users.
Last reviewed November 2, 2026
Overview
Quick facts about Reaction Commerce (Open Commerce).
- Launched
- 2015
- Headquarters
- Formerly Santa Monica, CA · Now community-distributed
- Ownership
- Open source (Apache 2.0) · stewarded loosely by Mailchimp/Intuit since 2020
- Scale
- ~500-1,000 estimated active deployments
- Known for
- Pioneer of open-source Node.js + event-driven commerce. Acquired by Mailchimp in 2020.
Pros & cons
The honest breakdown.
What's great
- Open source (Apache 2.0) — no license fee
- Event-driven microservices architecture
- GraphQL-first API design
- Multi-tenant, multi-shop support
- Docker + Kubernetes native deployment
- Historically used by major enterprises before Mailchimp acquisition
What to watch for
- Mailchimp acquired Reaction in 2020 → active development slowed
- Project renamed to Open Commerce; community-maintained now
- Smaller community than Medusa/Saleor
- Documentation gaps compared to actively-developed platforms
- Mostly a legacy choice in 2026 — newer alternatives generally better
Reaction Commerce (now Open Commerce) was a leader in open-source Node.js commerce 2015-2020. Since Mailchimp's acquisition, development has slowed and the community maintains it. For new builds in 2026, Medusa or Saleor are the better open-source + headless picks. Only choose Reaction if you have existing infrastructure or a specific need its event-driven architecture solves.
Ideal for
Teams already running Reaction who want to stay on it. Advanced engineering teams specifically wanting event-driven, microservice-based commerce.
Skip it if
You're greenfield — Medusa (Node) or Saleor (Python) have more momentum, better DX, and active development.
Pricing plans
What each plan gives you (and what it costs).
Open Commerce (Open Source)
Free
Transaction fee: 0%
Best for
Teams with Node + GraphQL + Kubernetes expertise
- Full source code
- GraphQL API
- Event-driven architecture
- Multi-shop
💰 Costs the pricing page doesn't show
Budget for these on top of the subscription. They're normal — just not advertised.
Senior Node.js developers
$100-$220/hour
Reaction expertise is scarce; general Node devs are plentiful.
Kubernetes hosting
$200-$2,000/month
GKE, EKS, or self-managed K8s.
Fork + maintenance
$30K-$200K/year
Realistic engineering overhead for keeping a fork current.
Payment gateway fees
2.9% + $0.30
Stripe, Braintree integrations.
Real-world cost
What Reaction Commerce (Open Commerce) actually costs at your scale.
Subscription is just the floor. Here's realistic monthly total including apps, payment fees, and day-to-day tools — based on real stores we've built and maintained.
Revenue
$100K/year
~$400/mo
K8s hosting $200 + dev $200. Likely too much overhead at this scale.
Revenue
$1M/year
~$1,500/mo
Scaled K8s $500 + dev $1K
Revenue
$10M+/year
~$5K+/mo
Enterprise K8s + dedicated team + fork maintenance
Features
What's built-in, what's paid, what's missing.
Catalog & inventory
Checkout (via GraphQL API)
Multi-currency
Multi-shop
Event-driven microservices
Flagship feature
GraphQL API
Docker + K8s native
Pluggable identity (OAuth, SAML)
GraphQL playground
React starter frontend
Open-source plugin system
Modern documentation
Documentation has gaps post-2020
Operator dashboard
Multi-shop management
Advanced reports
Role-based access
Global readiness
Can you actually sell globally on Reaction Commerce (Open Commerce)?
Multi-currency, multi-language, local payment methods, regional tax compliance — the four pillars of international commerce. Here's where Reaction Commerce (Open Commerce) lands on each.
Countries
Global (self-hosted)
Currencies
Multi-currency
Languages
Multi-language
Tax compliance
VAT, GST, US sales tax via custom integration
Local payment methods supported
Strongest in
Weak in
How it compares
Reaction Commerce (Open Commerce) vs the main alternatives.
The head-to-head that actually matters — what each platform wins on, based on 19 years of delivering both.
Legacy event-driven vs modern composable.
Reaction Commerce (Open Commerce) wins on
- Event-driven architecture out of box
- Older enterprise references
Medusa wins on
- Active development
- Much larger community
- Better documentation
- Modern DX
- Managed hosting option (Medusa Cloud)
Node vs Python — both open-source headless.
Reaction Commerce (Open Commerce) wins on
- Node ecosystem familiarity
- Event-driven architecture
Saleor wins on
- Active development
- Better documentation
- Enterprise references (Breitling, Lush)
Migration
Moving in, and moving out.
What it actually takes to get onto Reaction Commerce (Open Commerce) — and how painful it is if you outgrow it later. No vendor lock-in surprises.
Moving to Reaction Commerce (Open Commerce)
Here's what it typically takes to migrate from common starting points.
Typical time
N/A — rare migration path
Typical cost
N/A
Migrating TO Reaction in 2026 is uncommon. More common: Reaction → Medusa migrations.
Leaving Reaction Commerce (Open Commerce) later
How hard is it if this isn't the right platform for you in 2-3 years? (Honest vendor lock-in reality.)
Data is yours. GraphQL schema translates well to other API-first platforms. Common migration path: Reaction → Medusa or Reaction → Saleor.
Social proof
Brands that run on Reaction Commerce (Open Commerce).
Historical: various DTC + B2B (pre-acquisition)
Mixed
Mid-marketCurrent active base is small (~500-1,000)
Mostly developer-led
SMBFAQ
People ask us this a lot.
Is Reaction Commerce still maintained?+
Partially. Mailchimp (now Intuit) acquired Reaction in 2020 and renamed the open-source project to Open Commerce. Development has slowed significantly post-acquisition. Community contributions continue but at a much reduced pace vs Medusa or Saleor.
Reaction vs Medusa for a new build?+
Medusa wins decisively in 2026 — more active development, better documentation, bigger community, modern DX. Reaction is a legacy choice. Only pick Reaction if you have specific event-driven microservice requirements and the engineering team to maintain fork.
What's unique about Reaction's architecture?+
Event-driven microservices. Each capability (cart, catalog, orders, payments) can run as a separate service communicating via events. Comparable to commercetools architecturally but open source. Overkill for most SMB/mid-market stores.
Can I get commercial support for Reaction?+
No official commercial support since the Mailchimp acquisition. Community support via GitHub + forums. For commercial support on similar architecture, consider commercetools (enterprise) or Medusa Cloud.
Should I migrate off Reaction in 2026?+
If you're running production Reaction stably, there's no urgent reason to migrate. If you're starting new work, choose Medusa or Saleor instead. If you're facing feature gaps or security concerns on your current Reaction install, planning a migration to Medusa is reasonable.
Find what's slowing your Reaction Commerce (Open Commerce) store down.
We've audited 500+ stores. Reaction Commerce (Open Commerce) has predictable failure modes — get the prioritized fix list specific to your store.
- 12 dimensions audited (performance, SEO, security, conversion + more)
- Done by Dharmendra (20 yrs, 500+ stores)
- Razorpay USD/INR · NDA-protected · 24-hr refund
Still unsure if Reaction Commerce (Open Commerce) is right for you?
Book a 30-minute call. I'll tell you honestly — even if the answer is "pick something else."
Book a call · $29