Cloud FAQ

Our status page inclues information about Craft Cloud and all our other web services. More information about health checks is available in the Cloud Status article.

A link to the status page is available in the footer of every page on craftcms​.com.

The Knowledge Base is the best place to find answers to your Cloud questions — in particular, our Getting Started guide and the Troubleshooting Common Problems on Craft Cloud are pathways into many platform concepts.

If you have questions about our software products, check out the Craft CMS or Craft Commerce documentation.

Your Craft Cloud subscription entitles you to complementary developer support! Start a new conversation from our contact page using the email associated with your Craft Console account, or email us directly at support@craft.cloud.

Response times will be similar to normal Craft CMS developer support — we assign priority to incoming issues and address them in an equitable way. We have support personnel in each of Craft Cloud’s regions (US, Canada, EU, APAC).

Information about our support tiers is available on the Developer Support page.

We welcome feature requests via the public discussion board, or via support@craft.cloud.

Nope! A Craft license is included with your Craft Cloud plan. It is valid for as long as your plan is in good standing.

You do need to purchase licenses for any plugins you use, via the in-app Plugin Store.

Yes! Check out the Roadmaps page. Our plans for Craft Cloud appear at the bottom of the page.

Yes! This is a perfect way to manage multi-site installations.

Each project gets one free domain, and unlimited subdomains; additional domains can be added for a fee.

We currently support connecting GitHub, Gitlab, and BitBucket repositories.

Craft Cloud requires Craft CMS 4.6.0 and PHP 8.1. Your composer.lock file determines what version of Craft gets installed; your PHP version must be defined in your project’s craft-cloud.yaml configuration file.

Yes, all Craft Cloud projects start with a free 7‑day trial. Read more about trials in our Billing article.

Craft Cloud plans require a valid payment method on file in your Craft Console account or organization. Monthly and yearly plans are available.

Read more about billing on Craft Cloud.

Metered resources are listed on our Cloud Quotas page. Technical limitations are covered in Cloud Services + Compatability.

Use of Craft Cloud is also subject to our Acceptable Use Policy and Terms of Service.

We currently have presence in North America (Oregon, USA), Canada (Quebec), Europe (Frankfurt, Germany), and Asia-Pacific (Sydney, Australia).

Read more about region support.

Yes. More information is available in our dedicated databases article.

All Craft Cloud projects are protected by our Cloudflare WAF, with a ​“reasonable” setup of default rules.

We make specific changes to the firewall as needs arise. Additionally, some customers have their own Cloudflare accounts in front of ours, that allow them to manage specific WAF rules before requests are passed to ours. Cloudflare refers to this as the ​“Orange-to-Orange” scenario.

Nope, sorry! Craft Cloud is serverless, and doesn’t use a traditional HTTP server like nginx nor Apache.

Craft Cloud’s serverless architecture means there is nothing to SSH into! Images are built during each deployment, and spun up and destroyed based on traffic — even though the ephemeral filesystem takes some getting used to, its inherent stability and security are an essential part of what makes Cloud such a great place to host your Craft project.

Yes! From any environment in Craft Console, select Commands, then type in the Craft command you want to run. We don’t allow arbitrary shell commands.

No, Craft Cloud only supports MySQL 8 and Postgres 15. If you are migrating a site to Cloud, make sure its database can be neatly imported into MySQL 8, first.

Currently, there is no automatic way to do this.

As a result of each environment being connected to a git repository, you can revert problematic commits and re-deploy. If changes were made to the database that need to be rolled back (say, via a migration), the database will need to be restored to an appropriate point. Migrations are only run once Cloud has finished building your application image. Failed builds are never deployed!

Read more about deployments and our build pipeline.

You can populate environments’ storage from whatever source(s) you want, but there is not currently an automated tool for this.

• Code: Select the same branch as another environment, and start a deployment.
• Database: Capture and download a backup, then restore it to the secondary environment.
• Assets: Manually copy files from one bucket to another. Read more about synchronizing assets.

Database and asset access credentials can be retrieved from your Craft Cloud console on a per-environment basis from the Access menu.

Nope! SSL is included with every domain connected to your Craft Cloud project.

Yes! Please send us an email at support@craft.cloud to get started.

We currently do not have a dedicated transactional email service. You are free to use any Craft-compatible mailer adapter or SMTP service.

We cover customizing Craft’s mailer in the documentation.

Yes! Read all about deployments and the build pipeline.

Craft Cloud has a built-in static caching system that is designed to work seamlessly with Craft CMS. On-disk and rewrite-based caches will not work, as the Cloud filesystem is ephemeral — and files in the ​“web root” aren’t directly exposed to the web.

The Cloud filesystem has a special ​“fallback” feature for working locally.

Check out our migration guide! As long as you are using Craft CMS 4.6.0 or later, your project is apt to work on Craft Cloud with very few changes.

We only offer SLAs with enterprise agreements in place. Send an email to support@craft.cloud to get started.