Medusa.js development for teams that outgrew their platform
Medusa.js is an open source e-commerce platform that we shape around the way you sell: B2C stores, B2B platforms and multi-channel solutions.
20 minutes online. You get a straight answer: buy, build or drop it.
- Medusa’s ready modules
- Your sales logic
- One foundation
- Platform
- Medusa.js (open source)
- Pricing
- A fixed price for an agreed scope
- First step
- A 20-minute conversation
We contribute to Medusa and show a working store built on it.
When Medusa makes sense
Your own sales rules
Prices, discounts, buyer roles or the order flow do not fit the settings of an off-the-shelf platform.
Integrations at the core
The store has to work with ERP, PIM, WMS or partner systems, not just email orders to your team.
More apps instead of solutions
Every change needs another paid app, and the apps start to get in each other’s way.
Several channels, markets or stores
B2B and B2C, several brands or countries that should share one catalogue and one set of logic.
What you get
Architecture that fits your process
We separate what Medusa provides, what comes from our reusable implementation base and what has to be written for your business. You do not pay to rebuild things that already exist.
A storefront designed for buying
We design the storefront, usually in Next.js, around the buyer’s path: from categories and search to cart and checkout.
Your own sales logic
We extend Medusa modules and workflows with the pricing, order, role and availability rules your company needs.
Integrations with your systems
We connect payments, shipping, ERP, PIM and other systems so data flows automatically.
An admin your team can use
We extend the Medusa admin with the views and actions your team actually needs day to day.
Launch and growth
Production deployment, monitoring, documentation and full access to the code. After launch, we keep developing the store in stages.
How we work
Conversation
20 minutes with the founders: how you sell, what you want to change and whether Medusa fits the project.
Scope and fixed price
We agree the first stage and quote it at a fixed price. A live store on our foundation launches in 30 days.
Working increments
We show each stage on your own sales scenarios, not only at acceptance.
Release
We test the critical paths, move the data and launch the store following a cutover plan.
Growth
After launch, we develop the store in further stages, each with an agreed scope and price.
Technology
Medusa is our specialisation. We choose the rest of the stack to fit the project, its integrations and your plans.
- Medusa
- Next.js
- Node.js
Medusa vs Sylius, PrestaShop and Magento
Medusa is not the only sensible choice. Before we propose an implementation, we compare it with the platform you already run or the one another agency is quoting you. Here is the short version of what we say in the first conversation.
Sylius and Medusa are both open source platforms built around a company's process. They differ in the stack: Sylius runs on PHP and Symfony, Medusa on Node.js and TypeScript. What matters to you is who maintains the code after launch and what the features outside the core cost. In Sylius, some of them (B2B Suite, RBAC, multi-source inventory) sit in the paid Sylius Plus. In Medusa, customer groups, price lists and sales channels are in the open core, and the paid Enterprise edition covers RBAC and SSO.
| Platform | When it remains a good choice | When we propose Medusa |
|---|---|---|
| Sylius | You have a team or partner experienced in PHP and Symfony, and the plan is a longer project with Sylius Plus modules. | You want a live store in 30 days on a TypeScript stack, with an open B2B core and the code in your repository from day one. |
| PrestaShop | You sell retail, the catalogue fits standard modules and the budget does not justify custom code. | You have outgrown it: the store runs on 1.7, which is no longer maintained, per-customer discounts do not work from groups and the ERP integration depends on a third-party connector. |
| MagentoAdobe Commerce | You have a large catalogue, a Magento team and the budget for maintenance, upgrades and, on Adobe Commerce, the licence. | Maintenance, upgrade and licence costs grow faster than sales, and most extensions replace features you rewrite anyway. |
| ShopifyBigCommerce | You sell in a standard way, and a subscription with ready integrations is enough and does not block change. | Every new sales rule needs another app or a workaround, and revenue-based fees and add-ons grow every year. |
Medusa is a headless platform
Medusa is headless by design: the commerce engine exposes an API, and the storefront is a separate application, usually built in Next.js. The buying path is therefore not shaped by a theme, and a B2B portal or an app can sell from the same engine.
The storefront is also a second application to build, host and maintain, so we include it in the scope and the price from the first conversation.
Alufix: a complete purchase journey on Medusa.js
A B2C store built end to end on Medusa.js: catalogue, search, cart and the step into checkout. You can open the store and check the journey yourself.
Read the case studyEngagement model: fixed price
We work at a fixed price for an agreed scope. Before we start, you know what each stage delivers and what it costs.
The price mainly depends on the number and complexity of integrations, the data migration scope, custom sales logic and the interface design scope.
A live store on our foundation launches in 30 days, from €5,000 net.
Live e-commerce in 30 daysQuestions about Medusa.js
What is Medusa.js?
It is an open source e-commerce platform written in Node.js and TypeScript. It provides ready commerce modules (products, cart, orders, payments, customers, pricing) that can be extended and combined with your own logic. The storefront is built separately, so it can follow any purchase journey.
Is Medusa free?
The core of the platform is open source under the MIT licence, so there is no licence fee or revenue share. The exception is Enterprise features such as RBAC (roles and permissions) and SSO, which need a paid Enterprise licence or the Enterprise plan on Medusa Cloud. We build on the MIT core and tell you upfront if a project would need them. The costs are implementation, hosting and development, which is why we compare Medusa with SaaS over the full period of ownership.
Medusa or Shopify?
Shopify is a good choice for standard B2C sales when its settings and apps are enough. Medusa wins when you need your own pricing, order or integration logic, full control over data and code, or one foundation for several channels.
Medusa or Sylius?
Both are open source and both are built around a company's process. Sylius runs on PHP and Symfony and sells features such as the B2B Suite, RBAC and multi-source inventory in the paid Sylius Plus. Medusa runs on Node.js and TypeScript, keeps customer groups, price lists and sales channels in the open core, and its paid Enterprise edition covers RBAC and SSO. We choose Medusa because we build the backend and the storefront on one TypeScript stack, and a store on our foundation launches in 30 days. Sylius makes sense when you have a PHP and Symfony team that will maintain the code after launch.
Do you migrate stores from PrestaShop and Sylius to Medusa?
Yes. From PrestaShop most often when the store runs on 1.7, which no longer receives patches, and upgrading to 8 or 9 does not solve the problem with per-customer discounts or the ERP integration. From Sylius when the original agency has left and Symfony and PHP upgrades eat the development budget. In both cases we first check whether a migration is really needed.
Is Medusa a headless platform?
Yes. Medusa’s commerce engine exposes an API, and the storefront is a separate application, usually built in Next.js. You can design the buying path freely and connect more than one front end to the same engine. The storefront is a second application to build and maintain, so we include it in the scope and the price from the start.
Is Medusa suitable for B2B?
Yes. Medusa supports customer groups and price lists, and its modules can be extended with company accounts, spending limits, order approvals and quote requests. We describe the details on the B2B page.
Where does a Medusa store run?
On your own cloud infrastructure or on the managed Medusa Cloud hosting. The choice depends on your data requirements, costs and team. We settle it while defining the scope.
How much does a Medusa implementation cost?
A live store on Medusa and our foundation starts from €5,000 net and launches in 30 days. A larger scope, such as ERP integrations or a migration, is quoted at a fixed price after a conversation.
Let’s check whether Medusa fits the way you sell.
20 minutes with the founders. We will tell you plainly if an off-the-shelf platform is the better choice.