Deployment

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.

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 (v14 or v16) Odd-number releases of Node are not supported (e.g. v13, v15).
• 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):

Hardware	Recommended	Minimum
CPU	2+ cores	1 core
Memory	4GB+	2GB
Disk	32GB+	8GB

• A supported database version:

  Database	Recommended	Minimum
  MySQL	8.0	5.7.8
  MariaDB	10.6	10.3
  PostgreSQL	14.0	11.0
  SQLite	3	3

🤓 Database deployment

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

• A supported operating system:

Operating System	Recommended	Minimum
Ubuntu (LTS)	22.04	20.04
Debian	11.x	10.x
CentOS/RHEL	9.x	8.x
macOS	11.0	10.15
Windows Desktop	11	10
Windows Server	2022	2019

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', '0.0.0.0'),
  port: env.int('NODE_PORT', 1337),
});

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

APP_HOST=10.0.0.1
NODE_PORT=1338

💡 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:

yarn

NODE_ENV=production yarn build

npm

NODE_ENV=production npm run build

windows

npm install cross-env

Then in your package.json scripts section:

"build:win": "cross-env NODE_ENV=production npm run build",

And run:

npm run build:win

Run the server with the production settings:

yarn

NODE_ENV=production yarn start

npm

NODE_ENV=production npm run start

windows

npm install cross-env

Then in your package.json scripts section:

"start:win": "cross-env NODE_ENV=production npm start",

And run:

npm run start:win

✋ Caution

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();

✋ Caution

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:

🗃️ Other Hosting Guides

5 items

🗃️ Optional Software Guides

4 items