Infrastructure
What the infra under every Space does for you, from failover and edge protection to certificates and server settings
Spacefast runs on the same infra as WordPress.com and Pressable. Most of it needs no setup from you. Certificates renew automatically, failover moves traffic without a republish, and edge protection works without a plugin. These pages explain what the platform handles and the few parts left to you. Functions workers run separately and have their own outbound network rules.
Availability
Automated failover
Primary and secondary origins sit in different data centers. When the primary fails, traffic moves to the secondary without a republish or a DNS change.
Origin and edge servers
The edge receives requests close to your visitors. The origin handles the requests the edge cannot answer from cache.
Edge and traffic
DDoS protection
Anycast routing, edge caching, and traffic classification work without a setup step or a plugin in your Space.
Defensive Mode
Browser challenges reduce unwanted automated traffic. A challenge answers with HTTP 403.
Rate limiting
Tell an edge traffic limit apart from application capacity when a request gets HTTP 429.
Edge request logs
Cached responses, rate limits, and browser challenges, including requests that never reached your Space’s origin.
Security
TLS certificates
Spacefast provisions and renews HTTPS certificates for your Space’s hostnames automatically.
HTTP and security headers
Set your own security headers in _headers. The platform manages transport headers, including HTTP Strict Transport Security.
Filesystem permissions
A published version is an immutable snapshot. PHP filesystem permissions are a separate control over writes from PHP web requests.
Network and DNS
IP ranges
Use the DNS records Spacefast returns. Inbound addresses route visitors to the edge and do not identify the server running your Space.
Domain verification records
Most hostnames need only address records. A TXT record appears only when the hostname is already in use elsewhere.