Resource Allocation

Applies to: All

Overview

Resource allocation (on some enterprise and pro plans) lets org admins see total server capacity (CPU, RAM, cache) across all projects and assign limits per environment. Starter plans usually manage resources only on each environment’s Build Settings page instead.

Key concepts

  • Pool — shared capacity your plan includes across the whole organization.
  • Assigned — how much of that pool is reserved for specific environments.
  • Per-environment sliders — on Build Settings for each site copy; raising them spends credits and may draw from the org pool on eligible plans.

Do you have this feature?

If Billing does not show Resource Allocation, your plan adjusts resources only per environment — skip to Build Settings on each site.

Steps — review org capacity (when available)

  1. Open Billing.
  2. Locate Resource Allocation or plan capacity.
  3. Compare total pool vs assigned to environments.
  4. Identify over-provisioned staging copies eating capacity.

Per-environment defaults (typical)

New environments often start near: 1 CPU, 512MB RAM, 128MB Varnish, 128MB Redis included in the base creation fee. Production launches may need more — raise sliders on the live environment, not every dev sandbox.

Best practices

  • Match staging to production only when you load-test realistic traffic.
  • Downsize idle dev environments after projects ship.
  • Use Usage monthly to find environments with high CPU/RAM charges and no recent editor activity.

When to ask your account manager

Enterprise contracts sometimes include custom pooling rules or burst capacity — your dashboard labels may differ slightly from this guide.