Published on · Updated on: · By Vamsi Mullapudi
- 7 min read
Self-Host Medusa JS with AI | Deploy in One-Click With Kuberns
If you’re looking to deploy Medusa in production, you already know it’s not just another e-commerce template.
Medusa is an open source, headless commerce engine built for developers who want full control over their backend. You can customise pricing logic, extend APIs, manage orders, integrate custom payment providers, and connect any frontend framework like Next.js. That flexibility is exactly why many teams choose a Medusa self-hosted setup instead of a SaaS ecommerce platform.
Running Medusa in production is not just about starting a Node server. A proper deployment typically requires a PostgreSQL database, Redis for background jobs and caching, secure environment configuration, worker processes and HTTPS and domain setup.
If you try a typical Medusa Docker deployment, you’ll quickly notice that backend, worker, database, and Redis services all need to be wired together correctly. When hosting on platforms like Railway, Render, AWS, or DigitalOcean, you must manually provision and connect these components. That’s where deployment stops being about e-commerce and starts becoming an infrastructure project.
And this is the real question most developers end up asking: What is the easiest way to deploy Medusa without managing servers, containers, and background workers manually?
In this guide, we’ll break down how Medusa is typically deployed on other platforms, why it involves more setup than expected, and how you can launch a production-ready Medusa backend using AI-powered one-click deployment on Kuberns.
If your goal is to run a stable, scalable Medusa self-hosted backend without DevOps overhead, this guide will walk you through the simplest path.
TL;DR
- Medusa is an open-source headless e-commerce backend designed for full customisation.
- A Medusa self-hosted production setup requires PostgreSQL, Redis, secure environment variables, and background workers. Most deployment methods, including Docker, VPS, Railway, or Render, require manual configuration of these components.
- With Kuberns, you don’t have to do any manual configuration. AI handles container builds, runtime setup, networking, and production configuration automatically.
- You just have to fork the Medusa repository, add the required configuration, and clickdeploy to get live in one click.
Why Deploy on Kuberns? And How Medusa Is Deployed on Other Platforms
Deploying Medusa on Kuberns is built around a simple idea: you should not have to configure infrastructure just to run an ecommerce backend.
With Kuberns, Medusa deployment is AI-powered and one click. You start by selecting the Medusa template, forking the repository, adding the required configuration values, and clicking deploy.
The AI Agent automatically detects the application structure, prepares the correct runtime, builds the container, configures networking, and launches the backend in a production-ready state. You are not writing Dockerfiles. You are not provisioning Redis manually. You are not configuring reverse proxies or SSL certificates.
Now compare that with typical deployment methods.
If you deploy Medusa on AWS or DigitalOcean, you first provision a server. Then you install Node.js, configure PostgreSQL, set up Redis, configure environment variables, manage process managers, configure HTTPS with Nginx, and ensure worker processes stay alive. Every component must be connected correctly. A misconfigured Redis instance can break background jobs. An incorrect environment variable can block payment flows.
Platforms like Railway, Render, or Heroku simplify some parts, but you still need to attach databases, configure Redis add-ons, set memory limits, and define worker processes. These platforms reduce raw server management, but they do not remove application-level configuration complexity.
Medusa is not a static app. It is a commerce engine with background jobs, caching, and persistent storage requirements. Production deployment requires careful orchestration. Kuberns changes the model by combining one-click deployment with AI-assisted runtime configuration. Instead of manually stitching services together, you deploy Medusa as a complete system.
| Deployment Factor | VPS | Render / Railway / Heroku | Kuberns (AI One-Click) |
|---|---|---|---|
| Server Provisioning | Manual | Managed | Automated |
| PostgreSQL Setup | Manual install & config | Attach & configure | Pre-configured |
| Redis Setup | Manual install & config | Add-on configuration | Auto-handled |
| Environment Variables | Manual secure setup | Manual secure setup | Secure guided input |
| Worker Process Handling | Manual process manager | Manual config | Auto-configured |
| HTTPS & Domain Setup | Manual SSL & proxy | Platform-managed | Automatically enabled |
| Scaling & Restarts | Manual monitoring | Platform dependent | Auto-managed |
| Infrastructure Maintenance | High | Medium | Minimal |
| DevOps Knowledge Required | High | Medium | Low |
Other platforms give you infrastructure and expect you to assemble Medusa correctly. Kuberns assembles Medusa correctly and gives you the infrastructure automatically. That is the difference.
Deploy Medusa on Kuberns in One Click
Deploying Medusa on Kuberns is designed to give you full backend control without forcing you to manually configure databases, Redis, worker processes, or server infrastructure.
Instead of assembling multiple services yourself, you start with a pre-configured Medusa deployment template built specifically for production use.
Let’s walk through the process.
Step 1: Select the Medusa Template
Start by navigating to the Templates page. From there, choose the Medusa one-click template and click Deploy.
The template is already structured for production deployment. The runtime configuration, backend setup, and service handling are pre-configured. You are not starting from scratch or wiring together backend and cache services manually.
Step 2: Fork and Connect Your Repository
Before deployment continues, fork the Medusa starter repository into your GitHub account.
Forking gives you full ownership and customisation freedom. Medusa is designed to be extended, whether you’re modifying product logic, adding plugins, or integrating custom payment providers. By deploying from your own repository, you maintain complete control over your e-commerce backend.
After forking, connect your GitHub account in the Kuberns dashboard and select your forked repository. All future builds will be generated directly from your source code.
Step 3: Add the Required Environment Variables
For Medusa deployment on Kuberns, only two environment variables are required.
| Environment Variable | Purpose |
|---|---|
| ADMIN_EMAIL | The email used to create your Medusa admin account |
| ADMIN_PASSWORD | The password for accessing the Medusa admin dashboard |
These credentials are used to initialise your admin panel during deployment.
Unlike traditional Medusa self-hosted setups, where you manually configure database URLs, Redis endpoints, worker modes, and backend secrets, Kuberns abstracts the infrastructure layer. You only provide the admin credentials needed to access your store dashboard.
Step 4: Click Deploy
After connecting your repository and adding the two required variables, click Deploy.
Behind the scenes, the AI Agent:
- Builds the Medusa backend container
- Configures the production runtime
- Prepares service orchestration
- Injects environment variables securely
- Enables HTTPS automatically
- Launches your backend in production mode
You do not configure Redis manually. You do not wire up background workers. You do not manage reverse proxies. You do not handle SSL certificates.
When deployment completes, your Medusa backend is live and accessible via a secure URL. You can log in immediately using the admin credentials you provided.
Instead of offering generic hosting, Kuberns uses AI-powered deployment automation designed to understand application structure. When you deploy Medusa, the system prepares the correct runtime, configures service orchestration properly, injects environment variables securely, and launches the backend in a production-ready state.
Deploy Medusa on Kuberns Today
If you are building with Medusa, you likely chose it because you want full control over your e-commerce backend. You want flexibility, customisation, and ownership. What you probably did not sign up for is managing Redis instances, debugging container builds, configuring reverse proxies, or worrying about worker processes in production.
With Kuberns, you keep the advantages of a Medusa self-hosted backend while removing the infrastructure burden.
No manual server setup. No Docker orchestration headaches. No Redis wiring. No SSL configuration. Just a production-ready Medusa backend running in minutes.
If you are evaluating the best way to deploy Medusa without increasing operational complexity or hidden hosting overhead, this is the easiest path forward.
Deploy Medusa on Kuberns and launch your e-commerce backend with AI-powered one-click deployment.
FAQs on Medusa JS
What is the best way to deploy Medusa in production?
The best way to deploy Medusa in production is to use Kuberns AI that handles runtime configuration, HTTPS, environment management, and backend orchestration automatically. Traditional VPS or Docker setups require manual database and cache configuration. AI-powered deployment platforms like Kuberns simplify this by preparing a production-ready Medusa backend with minimal setup.
Where should I host Medusa?
Medusa can be hosted on AWS, DigitalOcean, Railway, Render, or other cloud providers. However, these options require manual configuration of services and environment variables. If you want to deploy Medusa without managing infrastructure directly, using one-click deployment platform, Kuberns, reduces complexity significantly.
Is there a one-click way to deploy Medusa?
Yes. Kuberns provides one-click Medusa deployment where you fork the repository, connect it, add required credentials, and deploy without configuring servers manually. This significantly reduces setup time compared to VPS or Docker-based deployments.
How long does it take to deploy Medusa?
Manual deployments using VPS or Docker can take anywhere from 30 minutes to several hours, depending on configuration. With AI-powered one-click deployment, Medusa can be live in minutes.