Acquia Cloud Free is built on the same infrastructure as Acquia Cloud Professional, so you can use the Acquia Cloud documentation to learn how to use it. As a general rule, you can use Acquia Cloud Free to do anything you could do on Acquia Cloud Professional, subject to the limitations listed on this page.
If you have an Acquia Cloud Free subscription, your use of Acquia Cloud is subject to some feature limitations, which you can remove at any time by upgrading to a paid subscription.
Upgrading to a paid subscription
To upgrade to a paid subscription, simply click the Upgrade link in the empty Prod environment on your subscription's Environments page. You can then select your new hardware and other Acquia Cloud features.
Compare what you get with free or paid Acquia Cloud:
|Two environments: Development and Staging; no Production environment||Three environments: Development, Staging, and Production (Acquia Cloud Enterprise subscriptions can request additional environments). Learn more.|
|No custom domain names||You can assign custom domain names to your environments. Learn more.|
|Servers have limited CPU and disk storage. Your application's codebase, database, and file system are each limited to 1 GB of disk storage. See Managing disk storage for Acquia Cloud Free for information about how to work within the storage limit.||Depending on your subscription level, shared or dedicated servers with a wide range of CPU, memory, and storage capacities are available. Learn more.|
|No support for Memcached, a general-purpose memory cache server daemon||Improve website performance using Memcached, which moves Drupal's standard caches out of the database into memory and caches the results of other expensive database operations.|
|You cannot send email from Acquia Cloud Free websites. You can use an external third-party email service instead.||Your websites can send limited outgoing emails such as Drupal registration confirmation emails and node subscription emails. You cannot send mass emails such as marketing messages or newsletters. You should use external email services for mass mailings. Learn more.|
|You cannot use SSL (HTTPS) to serve your application.||You can set up your application to use SSL (HTTPS). Learn more.|
|You must use Git to manage your code repository.||You can use either Git or SVN to manage your code repository and can migrate between SVN and Git. Use of Git is recommended. Learn more.|
|Your application is available as long as you're actively developing it. See Activity requirement for details.||Your application is available as long as you pay for it.|
|Insight provides many, but not all, available alerts and more limited website analysis. Insight reports can't be downloaded.||Insight provides the full range of available alerts and website analysis. Insight reports are downloadable.|
|Support unavailable from the Acquia Support team.||Support available from the Acquia Support team, with different levels of support.|
Activity requirement for free subscriptions
To keep your Acquia Cloud Free subscription, you must be actively developing it. A subscription is inactive if, in a 60-day period, there have been no code commits to your code repository. At 30 days and 45 days of inactivity, Acquia will email subscription owners to remind them to continue to develop their applications to ensure that the Acquia Cloud Free applications remain available. If an application is inactive for 60 days, the application is archived as a website archive file and is then removed from Acquia Cloud.
If you're a subscription owner, be sure to check your spam folder for application inactivity emails from Acquia.
As a free offering, Acquia Cloud Free does not entitle you to live or ticketed support. This is the case even if you also have a paid Acquia Cloud subscription. For more information about your Acquia Cloud Free subscription, review its documentation.