Skip to main content


Strapi provides many deployment options for your project or application. Your Strapi applications can be deployed on traditional hosting servers or your preferred hosting provider.

The following documentation covers how to develop locally with Strapi and deploy Strapi with several common hosting options.

☁️ Strapi Cloud

Don't want to deploy Strapi by yourself? Use Strapi Cloud to easily deploy and host your project.

🤓 Community Guides

In addition to the official deployment guides maintained by Strapi that are found here, community-maintained guides for additional providers are available in the Strapi Forum.

💡 Tip

If you already created a data structure with the Content-Type Builder and added some data through the Content Manager to your local (development) Strapi instance, you can leverage the data management system to transfer data from a Strapi instance to another one.

Another possible workflow is to first create the data structure locally, push your project to a git-based repository, deploy the changes to production, and only then add content to the production instance.

General guidelines

Hardware and software requirements

To provide the best possible environment for Strapi the following requirements apply to development (local) and staging and production workflows.

  • Node LTS (currently v16, v18, and v20) Odd-number releases of Node are not supported (e.g. v17, v19).
  • NPM v6 (or the version shipped with the LTS Node versions)
  • Standard build tools for your OS (the build-essentials package on most Debian-based systems)
  • Hardware specifications for your server (CPU, RAM, storage):
CPU2+ cores1 core
  • A supported database version:
🤓 Database deployment

Deploying databases along with Strapi is covered in the databases guide.

  • A supported operating system:
Operating SystemRecommendedMinimum
Ubuntu (LTS)22.0420.04
Windows Desktop1110
Windows Server20222019

Application Configuration

1. Configure

We recommend using environment variables to configure your application based on the environment, for example:

// Path: ./config/server.js

module.exports = ({ env }) => ({
host: env('APP_HOST', ''),
port:'NODE_PORT', 1337),

Then you can create a .env file or directly set environment variables in your chosen deployment platform:

💡 Tip

To learn more about configuration details, see the configurations documentation.

2. Launch the server

Before running your server in production you need to build your admin panel for production:

NODE_ENV=production yarn build

Run the server with the production settings:

NODE_ENV=production yarn start

We highly recommend using pm2 to manage your process.

If you need a server.js file to be able to run node server.js instead of npm run start then create a ./server.js file as follows:

path: ./server.js

const strapi = require('@strapi/strapi');
strapi(/* {...} */).start();

If you are developing a TypeScript-based project you must provide the distDir option to start the server. For more information, consult the TypeScript documentation.

Advanced configurations

If you want to host the administration on another server than the API, please take a look at this dedicated section.

Deployment Guides

Manual guides for deployment and optional software: