Skip to content

Commit 2ebd1fe

Browse files
authored
Add FAQ entry about Strapi Cloud upgrade (#2140)
1 parent da26c38 commit 2ebd1fe

File tree

1 file changed

+4
-0
lines changed
  • docusaurus/docs/dev-docs

1 file changed

+4
-0
lines changed

docusaurus/docs/dev-docs/faq.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,10 @@ If you used `--quickstart` to create your Strapi project, by default this uses t
3737

3838
It is recommended you use a database add-on like Heroku's PostgreSQL. For file uploads, you will need to use one of the 3rd party providers such as Cloudinary or AWS S3.
3939

40+
## How can I upgrade my free Strapi Cloud trial to a paid plan?
41+
42+
Strapi Cloud provides a free, 14-day trial. Whenever you're ready to upgrade to one of the [paid plans](https://strapi.io/pricing-cloud), please use the _Plans_ section of your Strapi Cloud project's settings (see [Cloud documentation](/cloud/projects/settings#upgrading-to-another-plan) for more details).
43+
4044
## Can Strapi be run in serverless environments?
4145

4246
Strapi is not well suited for serverless environments due to how the application is structured. Several actions happen while Strapi is booting that can take several seconds. Serverless deployment usually requires an application to cold boot very quickly. Strapi is designed to run as an always-on service, and we don't plan to decrease the cold boot time for the foreseeable future. Therefore, running Strapi in serverless environments is not a great experience, as every request will take seconds to respond to instead of milliseconds. Choosing between a cold boot or a warm boot is an architectural decision that many software developers need to take from a very early stage, so please consider this when choosing to use Strapi.

0 commit comments

Comments
 (0)