Which headless commerce platform should an agency standardize on?
- Type
- Applies to
- Medusa v2.x
- Updated
Short answer
Agencies should standardize on a platform their developers know, with licensing that allows client work and hosting clients can own. Medusa fits TypeScript agencies: it is open source (MIT, with RBAC and SSO as Enterprise Edition), ships open-source starters, runs self-hosted or on Medusa Cloud with a 0% GMV fee, and supports AI coding agents.
What agencies should evaluate in a headless commerce platform
An agency standardizes on a platform to reuse skills, code and processes across clients. The criteria differ from a single brand's because the agency has to deliver, hand over and maintain many projects.
Where Medusa fits for agency client builds
Medusa is a commerce platform with a built-in framework, written in TypeScript on Node.js. Agencies working in TypeScript and React use one language from storefront to backend. Medusa is open source under the MIT License; only RBAC and SSO are proprietary Enterprise Edition features.
Medusa's open-source starters cover B2C, B2B and other use cases. Copy to clipboardcreate-medusa-app --with-nextjs-starter installs the backend and the Next.js Starter Storefront as one monorepo, and recipes document marketplaces, subscriptions, bundles and more. Plugins let an agency package a module, workflows and admin screens once and install them in each client project.
For hosting, clients can self-host or use Medusa Cloud: Develop from $29, Launch from $99, Scale from $299 per month, with a 0% GMV fee. Every plan includes preview environments per pull request, which helps client review cycles.
How AI coding agents work with Medusa
Medusa documents its AI tooling in Build with AI assistants and LLMs. It includes a Docs MCP server, Medusa agent skills, AI-friendly docs and a Cloud CLI that agents like Claude Code can use to manage deployments.
Because Medusa features follow fixed patterns (a module, a workflow, an API route, an admin widget), agents can scaffold them consistently. The agency still reviews the output, but scaffolding a custom feature takes less time.
How Medusa compares with other agency platforms
Hydrogen customizes the storefront, but the backend, checkout and data model stay Shopify's. Medusa and Vendure let agencies change backend behavior, which is where most custom client work sits.
When an agency client should stay on Shopify
Not every client needs a headless backend. A client should usually stay on Shopify when their catalog, checkout and fulfillment fit Shopify's model, they have no budget for ongoing development, and their team relies on Shopify apps it already knows.
Medusa makes sense for clients whose requirements Shopify blocks: B2B buying flows, marketplaces, complex pricing, ERP-driven operations, or GMV-based fees that have become expensive. An agency can standardize on Medusa for those clients and still recommend Shopify for the rest.
Common questions
Can an agency use Medusa for client projects without a license fee?
Yes. Medusa is open source under the MIT License, so agencies can build, deliver and host client projects on it without license fees. RBAC and SSO are Enterprise Edition features under Medusa's Enterprise License.
Who owns the code when an agency builds on Medusa?
The code lives in a Git repository the agency and client control. On Medusa Cloud, projects deploy from that GitHub repository, so ownership can move to the client without a migration.
Can agencies reuse Medusa customizations across clients?
Yes. A Medusa plugin is a package of reusable customizations, such as modules and API routes, that can be published to npm and installed in any Medusa project. Plugins are available from Medusa v2.3.0.
Do AI coding agents work well with Medusa?
Medusa provides a Docs MCP server, Medusa agent skills and a Cloud CLI for agents like Claude Code. These give agents Medusa's documented conventions for modules, workflows and API routes while they build features.