How it compares, with a source on every row
Each page below reads the other product's own documentation, cites the page every claim came from, and opens with what that product does better. Where this engine is behind, the row says so.
Self-hosted platforms
vs Medusa Medusa has been public since 2020, is MIT licensed at its core, and has a plugin and module ecosystem this project does not have. Its admin supports right-to-left languages, which ours does not. If you want to build a bespoke commerce application on a framework with a large community, Medusa is the stronger choice and this page will not pretend otherwise. vs Vendure Vendure has been public since 2018, its core is GPLv3, and its plugin system and B2B feature set are more mature than anything here. If your team prefers GraphQL, or you need the B2B modelling Vendure is built around, it is the better tool and this page will not argue otherwise. vs Saleor Saleor is nearly a decade old, its core API and dashboard are BSD-3-Clause, and its app and webhook architecture is more scalable than anything here. It has an official payment app catalogue that this project cannot match. If you need a platform with that operational history, Saleor is the safer pick. vs EverShop EverShop is GPL-3.0 with no commercial tier, ships Stripe and PayPal as core modules where this engine ships neither, and scaffolds a running store with a single npx command. If you want a free licence with card payments already wired, EverShop gets you there faster. vs WooCommerce WooCommerce is GPLv3, free, thirteen years old, and has an extension marketplace nothing here can compare to. If you need an ecosystem, a hosting market and a hiring pool, WooCommerce wins outright. vs PrestaShop PrestaShop is open source under OSL-3.0, has been shipping since 2007, has an installed base this project cannot compare to, and supports right-to-left languages natively in both the front office and the back office. Its module marketplace is enormous. On ecosystem and track record it is far ahead of this project.
Hosted platforms sold to merchants
Salla and Zid are a different kind of product: a merchant subscribes and the vendor runs it. These two pages compare them with a self-hosted stack for the developer who builds stores for merchants, and say plainly when the hosted platform is the better answer.
vs Salla Salla is a mature Saudi platform with an ecosystem this project does not have: its own documentation calls it one of the largest ecommerce platforms in the region, its partner portal reaches tens of thousands of merchants, and the Twilight theme engine and app store sit on top of that. Payment methods Saudi shoppers expect are connected for the merchant. Nothing here replaces that convenience. What this engine is behind on, stated here because the row set on this page has no place for it: its first public release is not tagged yet, no card gateway ships in it, and its admin interface is English and is not mirrored for right-to-left languages, so a merchant who administers a store in Arabic reads an English dashboard. vs Zid Zid is an established Saudi platform with a partner ecosystem this project does not have: it publishes a merchant base in the thousands, a theme system with gettext localization and Arabic plural handling, an app market, and payment and shipping partners already connected. A merchant gets far more, faster, from Zid than from a self-hosted install. What this engine is behind on, stated here because the row set on this page has no place for it: its first public release is not tagged yet, no card gateway ships in it, and its admin interface is English and is not mirrored for right-to-left languages, so a merchant who administers a store in Arabic reads an English dashboard.
How these pages are kept honest
- Every claim about another product carries the URL it was read on and the words that support it. A claim the documentation does not state is marked as searched and not stated, rather than guessed.
- Every claim about The Merchant Engine links the documentation page that proves it, and those pages carry the file in the engine behind them.
- Each page opens with what the other product does better, and names where this engine is behind: a shorter history, no card gateway in the first release, and an admin interface that is not mirrored for right-to-left languages.
- The dates are on the pages. Other products ship; a row that has gone stale is a bug, and bbadii@pm.me is where to report it.
For what the engine itself does, read the feature pages or what an install puts on a box.
Last updated . Every claim on this page is read from a published source and cited beside it.