Deploy Strapi


Strapi is an open source headless CMS built with Node. It comes with a great admin UI that lets your entire team create and manage content for your websites and apps. Strapi makes your content available via an API and can therefore be used in many different ways.

Depending on how you’re using Strapi, your needs will vary when you deploy your project to production. In this guide we’ll describe three different methods you can use to deploy Strapi on Render, and help you pick the best one for your project.

You only have to make two choices:

  1. The database you will use to store structured content.
  2. The storage option you will use for image and video files uploaded through Strapi.

These choices determine the scalability, availability, and cost of your deployment.

In choosing the right Render plan for your Strapi web service, consider Strapi’s recommended requirements. Strapi also recommends setting up a proxy server for SSL and using pm2 to manage your Strapi server process. With Render, neither of these steps is necessary. All Render sites and services come with fully managed and free SSL, and Render services are automatically restarted if they become unresponsive.

Optimize for Cost and Simplicity

The simplest deployment method uses a web service with an attached persistent disk. The disk will store both a SQLite database file and uploaded media files. This approach is straightforward and inexpensive, but using a disk currently prevents horizontal scaling and zero downtime deploys. If you’re using Strapi as the data source for a static site generator like Gatsby or Hugo, these limitations shouldn’t be an issue for you because your service only needs to be available when you build your site.

Click the button below to see this approach in action. When you’re ready to create your own Strapi project, fork our Strapi with SQLite repository so you can add your own content types, plugins, and configuration options.


Deploy to Render

Optimize for Scale and Uptime

If you’re using Strapi as the backend for a website or app that dynamically fetches content, scalability and availability are more important. Our Strapi with PostgreSQL and Cloudinary repo is configured to use a managed PostgreSQL database for structured data and Cloudinary, a public cloud object store, for media file uploads. With this approach you’ll get zero downtime deploys and the ability to horizontally scale your Strapi web service. Your uploaded files will be served via Cloudinary’s CDN.

There are Strapi plugins for a number of object storage providers besides Cloudinary, including MinIO, which you can self-host on Render. See our 1-click deploy for MinIO.

To try this setup, create a Cloudinary account and make note of your cloud name, api key, and api secret. Cloudinary has a free tier that includes 1GB of storage. Click the button below and fill in your Cloudinary account details when prompted. Fork the repo when you’re ready to create your own project.


Deploy to Render

A Hybrid Option

If you care about performance but can tolerate a few seconds of downtime when you deploy, you can cut costs compared to a paid Cloudinary plan with the approach used in our Strapi with PostgreSQL repo. Here we’re using a managed PostgreSQL database along with block storage for media files. If your Strapi project doesn’t need uploaded media, remove the disk to get zero downtime deploys and the ability to add horizontal scaling.


Deploy to Render

Modify an Existing Strapi Project for Render

If you’ve been developing a Strapi project locally and are ready to deploy it to Render, follow these steps:

  1. Choose the approach that’s best for your needs and use the corresponding GitHub repo as a reference. You may find it helpful to look at the repo’s commit history.

  2. Depending on your approach, you may need to install some npm packages. For example:

    • pg for PostgreSQL
    • strapi-provider-upload-cloudinary for Cloudinary
  3. Copy the render.yaml file at the root of the Strapi on Render repo you picked in step 1. Consult our infrastructure as code guide to better understand what’s happening in this file.
  4. Copy config/env/production and its contents from the Strapi on Render repo you picked in step 1.
  5. Push your changes to GitHub or Gitlab and deploy with YAML from the Render dashboard.

Development → Staging → Production

When you deploy one of our Strapi on Render repos, your Strapi server will run in production mode. By design, Strapi’s admin UI doesn’t let you edit content types in production. Instead, you can set up separate environments for development, staging, and production, and edit your structured content types in development. Here’s the flow for creating and deploying your first content type:

  1. Fork one of our Strapi on Render repos and clone it on your local machine.

  2. Start Strapi in development mode by running yarn install && yarn develop on your local machine.
  3. Use the development admin UI, located by default at http://localhost:1337/admin, to create a new content type. Test by creating and fetching a few examples of this content type. Note that while content types are version controlled, your actual content is stored in a database and does not automatically transfer to other environments like staging and production.
  4. Push the changes to your remote GitHub repository.
  5. Deploy to a staging environment. Make sure you can create instances of the new content type.
  6. Deploy to production. You and your team will now be able to create instances of the new content type via your production admin UI.

If you’d like to set up a staging environment on Render, you can update the render.yaml file at the root of your repository and add staging resources that are similar to your production resources. You might want to change the name field to something like strapi-staging and the NODE_ENV environment variable to staging. You might also want to use less expensive service and database plans in staging. Finally, you can use Render’s pull request previews in addition to a permanent staging environment.