This is a guide for deploying a Medusa project to Qovery. Qovery is a Continuous Deployment Platform, that provides you with the developer experience of Heroku on top of your cloud provider (e.g. AWS, DigitalOcean).
It is assumed, that you are currently running a local instance of Medusa. If not, check out our Quickstart or useto set up your application in a matter of minutes. For the latter, see this guide for a small walkthrough.Copy to clipboardnpx create-medusa-app
1. Qovery Console
Create an account on Qovery on their free community plan and jump into the console.
2. Setup
Create a project and an environment.
3. Add your Medusa app
Add a new app to your Qovery environment and connect the Git repository that holds your Medusa project. In your application settings, set the port to 9000 unless something else is specified in your setup.
If you used ourstarter, your repository will most likely hold all components; storefront, admin and backend. Ensure that Root application path in Qovery is pointing to your Medusa project (Copy to clipboardnpx
).Copy to clipboard/backend
4. Add a database
Navigate to your environment overview and add the databases required by Medusa.
- Add Postgres database version 10, 11 or 12
- Add Redis database version 5 or 6
5. Configure Medusa
Our Medusa project needs a bit of configuration to fit the needs of Qovery.
Update Copy to clipboardmedusa-config.js
Copy to clipboard
medusa-config.js
First, add the Postgres and Redis database url to your
. In Qovery, click on your Medusa app in the environment overview. Navigate to environment variables in the sidebar on the left. Among the secret variables you should find your database urls. They should look something like this:Copy to clipboardmedusa-config.js
Add these to your
.Copy to clipboardmedusa-config.js
Furthermore, update
to include the following:Copy to clipboardmodule.exports
IMPORTANT: We are using the Qovery community plan, that does not allow SSL connections for the database, so this is disabled.In a production environment, you would need the following in the config:Copy to clipboarddatabase_extra: { ssl: { rejectUnauthorized: false } }
Add some extra variables
We need to add a couple of more environment variables in Qovery. Add the following variables in your Console with an application scope:
Make sure to use actual secrets in a production environment.
Update Copy to clipboardpackage.json
Copy to clipboard
package.json
Update
to the following:Copy to clipboardscripts
6. Deploy Medusa
Finally, deploy your Redis and Postgres followed by your Medusa application.
Deploy databases
In your environment overview in Qovery, deploy your databases one after the other. Only when these are deployed, proceed to next step.
Push changes to your repository
To initialise your first build Qovery, simply commit and push your changes.
6. Try it out!
In Qovery, click on your Medusa app in the environment overview. In the top right you are able to open up your application. Navigate to
to ensure, that the app is running.Copy to clipboard/health
What's next?
You now have an application running on Qovery. This can be scaled and configured to fit your business needs. As mentioned, we used the community plan, so this should be upgraded when moving to production.
Furthermore, you can deploy Medusa Admin for your application, such that you can start managing your store from an interface.
- Deploy Admin on Netlify
- Deploy Admin on Gatsby Cloud (Coming soon)
Share this post
Try Medusa
Spin up your environment in a few minutes.

You may also like
On this page