Platform Limits

Gatsby Cloud has several soft and hard limits to prevent abuse on our platform. These limits apply separately to use of Builds and Hosting. Gatsby may take action to reduce or limit your usage and whenever possible, we’ll let you know before we take any action. Below is a guide to the general limits that we expect most users to fall below for each plan.

Build Limits

Running into memory errors? See Why does my build encounter “Out of Memory” errors?

Hosting Limits

The above limits are upgradeable on an ad hoc basis for a Professional plan. These limits serve as a guide to help you pick the right plan for your needs. Visit our pricing page to see more details about what’s included in each plan and what plan might be right for your use case.

Functions Platform Limits

Serverless Functions on Gatsby Cloud are included in all plans with increasing monthly allotments based on the plan.

SSR/DSG limits

On the free tier, If none of the sites in the organization get any SSR/DSG requests for seven(7) days, the service will be scaled to 0. The next time a request comes in, it will scale back up. This first request will be slower than a normal request. After that, the service will stay scaled up for a minimum of 7 days again (every request resets the 7 day counter). 

For professional plans, the duration is 14 days and Enterprise never scales down.

Resource Timeouts

Gatsby Cloud terminates cloud resources when the customer’s cloud container does not create a build within a timeout period. For the Performance and Enterprise tiers, this timeout is applied differently between Builds and Gatsby Preview. These timeout limitations across all tiers are subject to change at the discretion of Gatsby, Inc. We reserve the right to adjust these limitations at anytime.

The timeout periods for each pricing tier are listed below:

*Preview timeout period only applies to the legacy CMS Previews experience. Currently, the following source plugins use legacy previews:

• gatsby-source-sanity
• gatsby-source-wordpress < 5.2.3
• gatsby-source-datocms < 2.6.15

When Gatsby Cloud terminates your resource after the timeout period, the next build will require restarting your resources. Typically in cloud infrastructure, this would mean a cold build, but each Gatsby Cloud build saves the Gatsby Cache to cloud storage. Upon restarting your resource we restore the previously saved gatsby cache to attempt a “warm” build. However, builds created after the timeout period may be slower depending on the state of the Gatsby Cache.

The Gatsby Cache works for both production builds as well as PR and CMS Previews. However, when the CMS Previews timeout, the URL for that preview will return an idle screen similar to the screenshot below. A Gatsby Cloud user can visit the link on that page to restart the preview for your content editors.