DEV.co
Open-Source Ecommerce · mercurjs

mercur

Mercur is an open-source, self-hosted marketplace platform built on top of Medusa.js that enables operators to run multi-vendor B2B and B2C marketplaces without SaaS fees or platform lock-in. It includes vendor onboarding, catalog management, commission handling, and automated payouts as built-in features.

Source: GitHub — github.com/mercurjs/mercur
1.6k
GitHub stars
400
Forks
TypeScript
Primary language
MIT
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repositorymercurjs/mercur
Ownermercurjs
Primary languageTypeScript
LicenseMIT — OSI-approved
Stars1.6k
Forks400
Open issues15
Latest releasev2.1.6 (2026-06-05)
Last updated2026-07-08
Sourcehttps://github.com/mercurjs/mercur

What mercur is

TypeScript/Node.js monorepo providing a modular, API-first marketplace engine (Mercur Core) layered on Medusa's commerce primitives, with independently deployable admin panel, vendor panel, and storefront components. Uses PostgreSQL, Redis, React, and Vite; event-driven, headless architecture designed for AI-assisted development.

Quickstart

Get the mercur source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/mercurjs/mercur.gitcd mercur# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Multi-vendor B2B/B2C Marketplaces

Ideal for operators who need vendor onboarding, multi-vendor catalogs where multiple sellers offer the same product, commission management, and payout automation without per-transaction platform fees.

Self-hosted, Data-sovereign Operations

Organizations requiring full control over marketplace data, infrastructure, customer relationships, and roadmap can deploy on their own servers, Kubernetes clusters, or managed cloud without vendor lock-in.

Custom, Headless Commerce Storefronts

Teams building branded or specialized customer experiences can extend Mercur via APIs and composable architecture without forking core, integrating with existing frontend stacks (React, Next.js, custom UIs).

Implementation considerations

  • Requires Node.js ≥20.x, PostgreSQL ≥13.x, and Redis; plan for containerization, container orchestration, and persistent storage setup.
  • Monorepo structure and modular architecture mean admin panel, vendor panel, and storefronts must be deployed separately; coordinate deployment pipelines.
  • Event-driven design and composable API-first approach necessitate clear understanding of marketplace workflows (vendor onboarding, offer/commission logic, payout rules) before customization.
  • Stripe Connect payout integration is built in; other payment and payout providers require custom integration via the API.
  • No built-in vendor KYC, EAN deduplication, or buy-box logic in open-source core; plan for in-house development or Mercur Enterprise license if these are critical.

When to avoid it — and what to weigh

  • Minimal DevOps/Infrastructure Appetite — Requires PostgreSQL, Redis, Node.js runtime, and container orchestration knowledge. Not a zero-ops SaaS; self-hosting demands infrastructure ownership and operational responsibility.
  • Simple Single-vendor Ecommerce — Mercur's multi-vendor and marketplace-specific features are overhead if you only need a basic product catalog and checkout. Consider lighter commerce solutions for straightforward use cases.
  • Immediate, Production-grade Enterprise Features — Advanced modules (EAN deduplication, Buy Box engine, vendor KYC, multi-channel sync) are part of Mercur Enterprise, not included in the MIT-licensed open-source core. Requires separate license and subscription.
  • Non-technical Operations Teams — Admin and vendor dashboards are included, but deployment, customization, and integration require technical engineering. Not suitable for non-technical operators without dedicated eng support.

License & commercial use

Licensed under MIT (MIT License), a permissive open-source license allowing commercial use, modification, and distribution with minimal restrictions. Source code is fully accessible.

MIT license permits commercial use and self-hosting without per-transaction or percentage-of-GMV fees. However, advanced enterprise features (EAN deduplication, vendor KYC, multi-channel sync) are part of Mercur Enterprise and require a separate commercial license and subscription. Verify Enterprise licensing terms directly with the Mercur team before relying on those features in production.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationAdequate
License clarityClear
Deployment complexityModerate
DEV.co fitStrong
Assessment confidenceHigh
Security considerations

Data owned and controlled by operator (self-hosted). No proprietary runtime or vendor-managed security audit details provided in data. Operators are responsible for PostgreSQL, Redis, Node.js, and infrastructure security hardening. Stripe Connect integration relies on Stripe's security for payouts. No explicit vulnerability disclosure policy or security audit log provided; requires review before production deployment.

Alternatives to consider

Medusa.js (Core Commerce)

Lighter-weight, single-vendor e-commerce foundation; Mercur builds on top. Use if multi-vendor complexity is not needed.

Shopify Plus / WooCommerce Multivendor Plugins

SaaS or managed solutions with vendor lock-in and transaction fees, but less infrastructure overhead and vendor-managed security. Choose if operational simplicity outweighs cost.

Sharetribe / Arcadier (SaaS Marketplaces)

Fully managed, turnkey marketplace platforms with built-in vendor features; no self-hosting required. Trade off data sovereignty and customization for faster time-to-market.

Software development agency

Build on mercur with DEV.co software developers

Mercur is production-ready and self-hosted. Get started with `bun create mercur-app@latest`, review the docs, or book a demo with the Rigby team for enterprise features and professional services.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

mercur FAQ

Is Mercur free to use?
The core marketplace engine is open-source under MIT license and free to self-host. Advanced enterprise modules (EAN deduplication, vendor KYC, etc.) require a separate Mercur Enterprise subscription.
Do I own my data and marketplace?
Yes. Self-hosted on your infrastructure with full source access. No per-transaction cuts, no GMV percentage fees, and no vendor lock-in. Your data, customers, and roadmap remain yours.
What's the difference between the open-source core and Mercur Enterprise?
Core includes vendor onboarding, multi-vendor catalogs, commissions, and payouts. Enterprise adds advanced features (EAN matching, Buy Box engine, vendor KYC, multi-channel sync) and comes with dedicated support, SLAs, and prioritized patches.
How hard is it to deploy and operate?
Requires Node.js, PostgreSQL, Redis, and infrastructure (containers or Kubernetes). Not a zero-ops SaaS. If you have engineering and DevOps resources, deployment is straightforward; without them, consider managed options or Mercur Enterprise support.

Work with a software development agency

From first prototype to production, DEV.co delivers software development services around tools like mercur. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across open-source ecommerce and beyond.

Ready to build your marketplace?

Mercur is production-ready and self-hosted. Get started with `bun create mercur-app@latest`, review the docs, or book a demo with the Rigby team for enterprise features and professional services.