Strapi Cloud

Promote environments to move content and configurations from one environment to another (e.g., from staging to production)

As a user, I would like to connect to my Strapi Cloud project's database to inspect, update, and pull data. Important: For users facing the same need, please note you can use an independent database with Strapi Cloud. For example, you could host your Strapi project on Strapi Cloud (and benefit from the easiness of deployment, the Node.js server, the assets storage, the CDN, and access to the Support team) with a database that is hosted on a separate platform, such as Neon, AWS RDS, etc. More information here: https://support.strapi.io/support/solutions/articles/67000718580-how-do-i-use-a-custom-database-with-strapi-cloud-

At the moment, Strapi Cloud offers two regions North America and Europe

Quite often users may want to have access to a Redis instance in Strapi Cloud and given how important it is to have the network latency between the app and Redis it would be nice if we could offer an add-on to allow users to have a Redis instance for use with plugins such as the REST Cache plugin.

Integrating the multi-environment feature to the CLI with functionalities like 'create an environment' or delete an environment'

Role-based permissions would give you control over who can access and modify each environment

To be able to have project or environment creation done asynchronously so that it's possible to use Strapi Cloud whilst it is being created in the background

Copy-paste environment variables to let you replicate environment-specific configurations (e.g., API keys, database settings) from one environment to another

Environment cloning so as to create an exact copy of any existing environment and its configurations

It would be great to be able to transfer a Strapi Cloud project from one user to another. This would be helpful for agencies transferring ownership of the project to their clients, or when a person is leaving a company.