Medusa Cloud features — what Medusa gives us for free (and what it costs)

Young, 2026-10-18: study Medusa's cloud features — Fix with AI, Emails, React Email, Clone Locally — for our Yukon IT product.

Context: we self-host Medusa on our prod node (Docker per tenant). Medusa Cloud is optional and bills per seat ($30/seat/mo). These features are Medusa's cloud offering — we study them to know what we're not buying and what we need to replicate ourselves.

1. Fix with AI (deployment troubleshooting)

What it is: when a build or deployment fails on Medusa Cloud, an AI agent analyses the logs, identifies the root cause, and suggests actionable fixes. Each build gets its own chat thread.

Our equivalent: we already have this. Our V3 fleet has observe.py, the restore proof, and the model router. The "Fix with AI" feature is essentially what Sol's diagnostic pipeline does manually — but Medusa's version is built into their cloud UI.

Cost to replicate: $0 — we already have the tooling. What we'd need is a tenant-facing UI that surfaces build failures with an AI-assisted explanation.

Verdict: not a competitive gap. We have better (our own agent fleet). But we should expose build failure diagnostics in the Yukon IT admin portal.

2. Medusa Emails (built-in email sending)

What it is: a built-in email sending service for Cloud projects. Transactional and marketing emails (order confirmations, etc.) sent directly from the Medusa application without setting up your own email infrastructure.

Key facts:

• Enabled by default for all Cloud projects, zero configuration
• Available for all Cloud plans (different sending limits per plan)
• Monitors email sending statistics via the organization dashboard
• Can manage sender domain verification
• Verified sender domains are available for Launch, Scale, and Enterprise plans only

Our equivalent: we use M365 Business Basic (AU$10.50/user/mo) for tenant email, and Brevo (free tier, 300 emails/day) for transactional email. Medusa Emails is a convenience feature that bundles email into the cloud offering.

⚠️ Correction (Echo, 2026-10-18): the Brevo free tier is verified (300 daily sends), but "we already have Brevo" is not — no Brevo configuration exists on LAB or prod, and prod runs no SMTP listener. Brevo is the proposed provider, not yet provisioned. See [medusa-cloud-engineering-verification](medusa-cloud-engineering-verification) §5. The verdict below holds; only the tense changes.

Cost to replicate: $0 — we already have Brevo (free) + M365 (priced). Medusa Emails would save us the Brevo setup but adds a Medusa Cloud dependency.

Verdict: not needed. Our email stack (M365 + Brevo) is cheaper and more flexible. But we should note that Medusa's built-in email is a selling point for customers who don't want to manage email infrastructure — and our "managed hosting" pitch already covers this.

3. React Email (email templates)

What it is: a library for creating email templates using React components, then rendering them to HTML for sending. Includes a preview server for development.

Dependencies: @react-email/components, @react-email/render, @react-email/preview-server, react-email (dev).

Caveat: newer versions of React Email are not supported due to Node version incompatibilities on Cloud. react and react-dom must be in dependencies (not devDependencies) or the deployment fails.

Our use: we can use React Email for our tenant email templates (order confirmations, welcome emails, password resets). It integrates with Medusa's Notification Module and works with both Medusa Emails and our own providers.

Cost: $0 (open-source library). But it requires Node.js in the tenant stack (already present via Medusa).

Verdict: adopt for tenant email templates. Low effort, high polish. Our tenants get professional email templates out of the box.

4. Clone Locally (dev workflow)

What it is: clone a Cloud project's GitHub repository to your local machine, install dependencies, set up environment variables, and run the Medusa application locally for development and debugging.

Prerequisites: Node.js v20.19.0+, Git, PostgreSQL.

Workflow:

1. Clone the repo from GitHub
2. npm install (match the lock file)
3. Create .env pointing at local resources
4. npx medusa db:migrate (run migrations)
5. npm run dev (start dev server)

Our use: this is exactly how our tenants (or we, on their behalf) would develop and customise a Medusa storefront. The clone-locally workflow is standard Git + npm — nothing proprietary.

Cost: $0. This is just Git.

Verdict: standard practice, no cost. We should document this workflow for our tenants in the KB (P1 product).

5. What Medusa Cloud offers that we DON'T have (and whether we need it)

6. The key insight: Medusa Cloud is a competitor to our hosting model

Medusa Cloud sells managed Medusa hosting at $30/seat/mo. We sell managed Medusa hosting at A$119/mo (Solo, all-in). The difference:

Medusa Cloud sells infrastructure. We sell an outcome. Same positioning as vs Hostinger, same conclusion: we are not competing on price for raw hosting.

7. What to take from Medusa Cloud (and what to leave)

Take (feature benchmark):

• "Fix with AI" for build troubleshooting — expose in our admin portal
• React Email for professional email templates — adopt for tenants
• Clone-locally workflow — document in our KB (P1 product)
• Preview environments — future feature, not pilot

Leave (do not copy):

• Medusa Cloud's pricing model ($30/seat) — our per-tenant model is better for small retailers
• Medusa Emails — we have Brevo + M365, cheaper and more flexible
• Medusa Development Agent — our EVE is tenant-tuned, theirs is generic

8. Cost impact on our business plan

Zero. These features don't change our pricing or capacity. They confirm that:

1. Our stack (Medusa + EVE + Nuxt UI + Docker) covers everything Medusa Cloud offers, plus POS and tenant-tuned AI.
2. The only thing we're missing is preview environments (not needed for pilot).
3. React Email is a $0 add that improves our email quality.

Honest limits

• Medusa Cloud pricing ($30/seat) is from their website; actual usage costs may vary. I did not sign up to verify.
• "Fix with AI" is a cloud feature — I have not tested it; I only read the docs.
• React Email version compatibility (Node v20.19.0+) needs verification against our Medusa v2.21.2 stack.
• I did not price Medusa Cloud's actual infrastructure costs (compute, storage, egress) — only the seat price is published.