Understanding the definition of a Strapi "project"
Last updated: March 3, 2025
What is a project?
A Strapi "project" is defined as a unique configuration of the Strapi software that:
Produces an identical Strapi API and content model structure
May be deployed across multiple environments
Can be scaled horizontally or vertically
Functions as a single application, regardless of instance count
Enterprise Edition licenses are distributed on a "per project" basis, with pricing based on the number of admin users.
Examples of valid project scaling
A single project may be scaled to handle large traffic through:
Vertical scaling
Running multiple instances on the same host
Using process managers like PM2 for instance scaling
Horizontal scaling
Deploying instances across multiple hosts
Using load balancers to distribute traffic
What is not considered a single project
The following scenarios require separate licenses:
Multi-tenancy applications with different models
Example: Client A has 4 fields in an "articles" model, while Client B has 5 fields
Multiple projects serving different websites
Example: One Strapi instance for client1.example.com, another for client2.example.com
Template projects available for distribution
Strapi starters
Strapi templates
How environments differ from projects
Your license allows unlimited environments for a single project. Examples include:
Development environment
Multiple developers working locally
Staging environment
Dedicated testing and content preview
Production environment
Load-balanced instances serving live content
Legacy environments
Maintaining older versions during migrations
For more information about user licensing, see:
📄 Key licensing definitions for Strapi Enterprise Edition