Same problem, opposite ends
- Zero GMV fees — The license is your only platform cost. Your success isn’t taxed.
- Own the source — Open source, full source for licensees – an engine you can read, audit, and extend.
- Your infrastructure — Any cloud, on-premise, or air-gapped. Data residency is your decision.
- Built on the most popular framework — Standard JavaScript and TypeScript – any web developer can work on it, no certified specialists to hire.
- Additive, not disruptive — Add a third-party layer without replatforming, or stand up a full marketplace from scratch.
- No vendor lock-in — Keep the version you paid for and everything built on it – forever.
Mirakl vs Mercur, by architecture
| Category | Mirakl | Mercur |
|---|---|---|
| Core technology | Closed, vendor-only | Open source (MIT), public |
| Enterprise code | Black box | Full source for licensees |
| Integrations | Separate products | Built into one platform |
| Customization | Tickets and workarounds | Your own layer, official extension points |
| Deployment | Vendor cloud only | Any cloud or on-premise |
| Cost model | A percentage of your GMV | Zero GMV fees |
| Exit | Lock-in | You keep what you paid for |
| Developer pool | Certified specialists | Any web developer |
Your success shouldn’t raise your bill
A percentage of GMV means the better your marketplace does, the more you pay – for the same platform, the same support, and servers you are already paying for yourself.
Whose data feeds your AI?
- Mirakl — Your data → Mirakl’s cloud → Mirakl’s AI.
- Mercur — Your data stays → your AI, your infrastructure.
When each one is the right call
Choose Mirakl
You don’t have your own vendors and you need a ready network of 100k+ merchants live in about 90 days.
Choose Mercur
- You bring your own vendors
- You want to own the code and the data
- You need on-premise or EU data residency
- You want a cost that doesn’t grow as a tax on your success