Medusa logo

Medusa development, headless commerce you own, with no platform fees.

Custom stores, marketplaces and B2B portals on Medusa, the open-source Node.js commerce engine, with your own front-end and business rules.

Fixed quote in 48 hoursNDA on requestYou own the code
src/workflows/apply-loyalty.tsRunning
export const applyLoyaltyWorkflow = createWorkflow(
  "apply-loyalty-points",
  (input: { cartId: string; points: number }) => {
    const customer = getCartCustomerStep(input.cartId);
    validatePointsStep({ customer, points: input.points });

    const discount = convertPointsStep(input.points);
    addCartAdjustmentStep({ cartId: input.cartId, discount });

    return new WorkflowResponse(discount);
  }
);
Workflow testedRollback steps definedStaging deployed
MedusaNode.jsNext.jsTypeScriptPostgreSQLStripeRedis
Medusa and the stack around it
NDA signedBefore any code is shared
Demo every sprintOn a staging link you can click
48 hrsto a fixed quote after the first call
~5 daysfrom brief to first commit
1–2 wkssprints, each ending in a live demo
100%code ownership once the work is paid for
What we build

Medusa, put to work.

The kinds of Medusa projects clients bring us most often.

Headless stores

Next.js storefronts on a Medusa backend you control.

Marketplaces

Multi-vendor catalogues, orders and payouts.

B2B commerce

Company accounts, approvals and custom price lists.

Custom modules

Loyalty, subscriptions or rental logic built in.

Multi-region selling

Currencies, taxes and fulfilment per market.

Platform migrations

Move off Shopify or Magento when you outgrow them.

Is it right for you?

When Medusa fits, and when it doesn’t.

We recommend the stack that suits the job, even when that means suggesting something else.

A strong choice when
  • Your rules do not fit Shopify's model
  • You want to own the code and avoid per-sale platform fees
  • You need a marketplace or unusual checkout
Think twice when
  • A simple store that Shopify would launch faster
  • Teams with no budget for hosting and maintenance

Not sure? Tell us about the project on a free call and we’ll give you a straight answer.

The stack around it

Works best alongside these.

What we most often pair with Medusa. Each has its own page.

How it works

From first call to first release.

  1. 30 minutes, free

    Discovery call

    You explain the goal. We ask about users, deadlines and what already exists.

  2. Within 48 hours

    Proposal & fixed quote

    Scope, Medusa architecture, timeline and price in writing.

  3. Every 1–2 weeks

    Sprints with demos

    Working software on a staging link at the end of every sprint.

  4. Launch week

    Launch & handover

    Go live together, then receive code, docs and a walkthrough.

Timings are typical and depend on scope. Your proposal states the exact plan. See how we work.

FAQ

Questions, answered.

More about hiring Medusa developers, pricing and ownership.

Browse all FAQs
Medusa or Shopify?

Shopify is quicker for standard stores. Medusa makes sense when you need custom rules, a marketplace or full ownership. We compare the total cost with you.

Who hosts Medusa?

You do, on your own cloud or Medusa Cloud. We set it up with backups and monitoring, and can look after it on a Care plan.

How quickly can Medusa developers start?

Usually within about five working days of agreeing the brief. You get a fixed quote within 48 hours of the first call, and work starts once the contract and NDA are signed.

How do you price Medusa work?

Scoped projects get a fixed price split into milestones, each paid when you approve its demo. For ongoing work you can hire dedicated developers monthly or by the hour. Current rates are on our pricing and hire-developers pages.

Who owns the Medusa code you write?

You do, once the work is paid for. Repositories and cloud accounts are set up in your name from day one, and you receive documentation and a recorded walkthrough at handover.

Can you take over an existing Medusa project?

Yes. We begin with a short audit of the code, hosting and open issues, share what we find in plain English, then agree a plan before changing anything.