Server specifications and settings
Managed hardware, PHP settings, and the configuration boundaries for a Space.
Spacefast manages the servers behind your Space. You publish files and configure application behavior; the infra handles hardware, replication, and the shared edge network.
Underlying infra
WP Cloud runs origin pools on AMD EPYC processors with NVMe storage and redundant 25 Gbit networking per server. Primary and secondary servers sit in different regions for automated failover. Hardware and software change as the platform upgrades pools.
Those are pool specifications, not dedicated resources reserved for each Space. Your product entitlements come from your plan limits.
PHP and compression
WP Cloud’s default PHP memory limit is 512 MB per request. The platform supports larger per-site values, but Spacefast manages the settings for its sites. A WP Cloud capability does not create a matching Spacefast configuration field.
The infra supports Brotli and gzip compression. A client that accepts Brotli can receive it; gzip is available as a fallback. Compression headers belong to the platform, so do not set Content-Encoding in your published header rules.
For application access to WordPress, use the documented WordPress commands and Abilities. The underlying PHP configuration is not a promise that arbitrary uploaded PHP files will execute.
Configuration boundaries
| Change | Spacefast path |
|---|---|
| Redirects, rewrites, and response headers | Publish _redirects, _headers, or the supported routing configuration. |
| Application environment variables | Use Environment variables. |
| Runtime configuration | Use the documented Zero runtime configuration. |
| Storage and resource entitlements | Check Limits. |
Spacefast rejects authored .htaccess and .user.ini files. You cannot replace the managed server configuration or php.ini through a publish. Use the supported configuration for the behavior you need.