Resource limits and quotas

The portal displays the exact orderability and configuration limits currently available to an App or Team. The following rules remain stable when numeric ceilings change.

Purchased shape

• The purchased CPU, memory, and storage amounts are the billing and enforcement envelope.
• Customer service reservations and platform workload floors must fit inside that envelope.
• A smaller shape is rejected if a required service minimum no longer fits.
• Storage can grow but can’t be reduced through self-service.

Memory classes

• MySQL, the Valkey session/cache/config-cache roles, OpenSearch, RabbitMQ, Varnish, and NFS are reservable services. Customer memory is the request and reservation, so these services don’t memory-burst past it.
• NFS is the exception: its reservation is the request and its limit is 1 GiB or the reservation, whichever is larger.
• PHP-FPM, Nginx, Scheduled Jobs, and the WAF are dynamic workloads. They have platform floor requests, no memory limits, and no customer memory fields.
• Dynamic workloads consume the unallocated headroom left after platform costs, service reservations, and workload floors. PHP-FPM worker count and OPcache derive from that headroom.
• Legacy dynamic memory fields are ignored on read and rejected on write with DYNAMIC_MEMORY_NOT_EDITABLE.

CPU burst

• The portal offers four spike modes: Always keep my site fast, Keep my site fast, with a spending limit, Never spend more than my plan, and Custom, per container.
• Custom, per container exposes Off, Capped, and Unlimited for CPU where the container class allows it.
• A cap is a multiple of the configured request, above 1× and inside the allowed platform range. The multiple is what’s stored, so a plan resize re-derives the cap.
• Burst use above the request is metered for its duration. A share of each month’s burst minutes is included at no charge.
• CPU burst choices apply to every container, managed services included. The Burst tab has no dynamic-workload memory control.

Storage expansion

• Database and workspace storage can use automatic expansion.
• Media storage isn’t automatically expanded by this control.
• Each expansion permanently raises the purchased amount.
• A configured ceiling is never silently exceeded.

Configuration counts

• An App can have up to 50 scheduled jobs.
• An App can define up to 50 domains.
• An App can have up to 32 SSH users.
• A Team can save up to 10 payment cards.
• A Team can have up to 50 active members by default, and support can raise a Team’s limit. The limit is enforced when an invitation is accepted; pending invitations don’t occupy a seat.

Configuration sizes

• A settings file can be at most 256 KiB.
• Each secret value must be 60 KiB or smaller.
• Maintenance-page assets and support attachments have their own size and format limits, listed with those features.

Source of truth

Use the limit shown in the portal for the current App or Team. App limits also depend on region, framework, and service catalog. If a documented numeric example differs from the portal, the portal’s validated value controls the accepted configuration.