Medusa Development

Medusa is an open-source commerce engine written in TypeScript. Kryeo builds on it: custom modules, workflows, pricing rules, admin extensions, and the integrations a real store needs, deployed to infrastructure in your name.

What Medusa is

Medusa gives you the commerce primitives (products, variants, pricing, carts, orders, fulfilment, payments, tax) as a set of modules running on Node.js and PostgreSQL. You extend those modules and add your own in TypeScript.

The parts we work with most:

• Modules: self-contained slices of domain logic (a custom loyalty system, a rental model, a made-to-order flow) that plug into the core.
• Workflows: durable, multi-step operations with compensation on failure. Order orchestration, ERP sync, and fulfilment routing live here.
• The admin: extensible with custom pages and widgets so your operations team manages everything from one place.
• The API: REST and GraphQL, consumed by the storefront and any other application.

What Kryeo builds on Medusa

• Custom modules for commerce logic that does not fit the standard model.
• B2B capabilities: price lists, customer-group pricing, quote and approval flows, purchase orders, net terms.
• Subscriptions: billing cycles, dunning, plan changes, proration.
• Admin extensions: the dashboards, bulk actions, and views your team needs.
• Integrations: ERP, PIM, 3PL, tax, marketing, and analytics, built as modules or workflow steps rather than brittle scripts.
• Deployment: Medusa and its worker, Postgres, Redis, and a CI pipeline, on a host you control.

How we approach a Medusa build

We model the domain first. Products, pricing, the order lifecycle, and every integration point are written down and agreed before code. Medusa's module boundaries make this concrete: each area of logic has a clear home.

The codebase is typed end to end. A new capability is a module or a workflow with tests where they earn their keep, not a patch to a monolith. That is what keeps changes cheap after launch, and what lets you hand the project to any TypeScript team.

Medusa vs a hosted platform

	Kryeo	Hosted platform (e.g. Shopify Plus)
Commerce logic	Change anything; it is your codebase	Customise within platform APIs and app extension points
Fees on sales	None	Percentage of revenue on higher tiers, plus payment fees
Hosting and updates	Your responsibility (or ours on retainer)	Managed by the platform
Vendor risk	None; open source, self-hosted	Pricing, limits, and roadmap set by the vendor
Best fit	Custom logic, high volume, or a need to own the stack	Standard commerce that fits the platform model

Working with us

Whether you need a full Medusa build, a specific module, a rescue of a stalled project, or a migration off a platform you have outgrown, tell us the shape of it and we will give you an honest read on scope.

Start a project →