What stack is The Merchant Engine built on?
A typed TypeScript stack: a NestJS API on PostgreSQL and Redis with Prisma, an Angular admin dashboard, and a server-rendered Analog.js storefront, installed together as a self-hosted ecommerce platform. The API is a REST surface, so a storefront in React, Vue, Svelte or anything else builds on the same endpoints: headless commerce when you want it, a finished storefront when you do not.
What do I need before installing?
For a server: a Linux box with Docker Engine and Compose v2, git and Node.js 22, DNS for the store, the admin and the API, an S3-compatible bucket, a Resend account with a verified domain, and a Cloudflare Turnstile widget. For a laptop: Docker Desktop, git and Node.js 22, nothing else. The full requirements.
Does it run on Windows?
The local profile does, through setup.ps1 on Docker Desktop. A server install runs setup.sh on a Linux box, because that is where the certificates and the timers live.
Is this just another no-code template?
No. It is a stack you install and build on: an API, an admin and a storefront with their source, not a page builder. You keep the code and change what you need.
Do I have to build a storefront, or is one included?
One is included: a server-rendered storefront with home, catalog, search, cart, checkout and customer accounts in French, English and Arabic with a mirrored layout for Arabic. Brand it from the admin and launch, or treat it as the reference implementation and build your own on the same REST API.
Which languages and currencies does it support?
French, English and Arabic: a store enables any pair or all three and picks a default, and the storefront mirrors its layout for Arabic. Any currency, with the symbol, its position, the separators and zero to three decimals set at install and served to every app from the store config.
Which payment and shipping providers are supported?
Cash on delivery, manual transfer, gift cards and card payment through Stripe are live, on an idempotent payment flow with webhook dedup. Stripe card payment is embedded in the checkout or on a hosted page, and the operator enters the keys in the admin. More card providers plug in behind one interface. Shipping is zone-based rates with carrier and tracking management.
Can't I just vibe-code this with AI?
You can get a checkout working with AI in an afternoon. The hard part comes after: race conditions on inventory, idempotent orders and payments, refunds and returns, webhook retries, access control and the security holes you only find once a store takes real money. The Merchant Engine is that part, already built, with the tests that prove it.
Do I keep control of the code, or is this a black box?
You get the source. The engine is open source under the MIT license, and the code runs on your box with no telemetry and no license server.
Can I use it on client projects and bill for it?
Yes. MIT allows any number of client stores, paid or not, with no fee and no license key. Install it once per client and bill for your work.
Is there telemetry?
No. Nothing on the box calls home.
It's v1. How stable is it really?
Every push runs the unit suites, the end-to-end suites against a real database, the lint, the production builds and an install smoke that runs the real installer twice on a fresh box. The counts on this page are read from the release, not typed.
How much does it cost?
Nothing. The engine is free under MIT. You pay only for your own hosting and the third-party services the store uses. If you want it built and run for you, hire Badii Studio.
Can someone build and run it for me?
Yes. Badii Boutar, who builds the engine, works as Badii Studio. He installs, customizes, hosts and maintains stores built on it, so you can hand over the whole tech side. Start at badii.studio/themerchantengine.
Who's building this, and why should I trust it?
Badii Boutar, a full-stack developer with three years of ecommerce work: ten or more client stores shipped, the number one livestock marketplace in Saudi Arabia, and Peeps at 85K+ installs. The engine is built in public and every claim on this page points at the code that proves it.