Build Settings and Credits

Applies to: Codeless

Overview

Build Settings control how much server power each environment gets — CPU, memory, and cache layers. Think “t-shirt sizing” for your site: larger sizes handle more visitors but spend more credits each month.

Key concepts

  • CPU — processing power for building pages and running background tasks.
  • RAM (memory) — workspace for Drupal; content-heavy sites need more.
  • Varnish — stores rendered pages for faster repeat visits (important on public marketing sites).
  • Redis — fast cache for Drupal internals; advisories often suggest increasing it when pages feel sluggish.

Steps

  1. Open Environments, select an environment, then Build Settings.
  2. Read the credit estimate before moving sliders.
  3. Increase modestly on production before launch traffic; keep dev copies small.
  4. Save and allow the platform to apply changes (brief restart possible).
  5. Re-run Quality to see if performance improved.

Defaults

New environments often start near 1 CPU, 512MB RAM, 128MB Varnish, 128MB Redis included in the creation fee.

When to upgrade

  • Slow Quick Login or public pages after content growth.
  • Site Alerts and Configuration Advisories recommending more Redis or cache.
  • Traffic spike expected after publication — scale production, not every dev sandbox.

Monitor Billing → Usage after changes. FROZEN orgs cannot increase resources until billing is ACTIVE.