# Fastly
Fastly (opens new window) provides an edge CDN in front of WordPress instances managed by PanelAlpha. Traffic reaches the origin only through Fastly, while DNS for customer domains continues to be managed by the DNS provider configured on the plan.
With Fastly enabled on a plan, PanelAlpha can automatically:
- create a Fastly service for the instance
- point the origin backend to the hosting server IP (without publishing that IP in public DNS)
- provision TLS at the edge
- sync Fastly-resolved DNS records (A / AAAA /
www/ ACME validation) to the plan DNS provider - install a WordPress MU-plugin for cache tags and automatic purge on content updates
Clients keep a simple interface: Purge Cache and Under Attack Mode.
# Prerequisites
- A Fastly account with an API token (opens new window)
- A DNS provider configured on the plan (for example Cloudflare or PowerDNS) so PanelAlpha can write the Fastly DNS records
- PanelAlpha v1.9.5 or later with the Fastly integration available
# Enable the Integration
Fastly starts as a hidden integration. Unhide it on the PanelAlpha server, then configure it in the Admin Area:
php artisan integrations:show fastly
- Go to Admin Area → Integrations.
- Find Fastly, enable it, and open Configure.
- Paste the Fastly API Token.
- Run Test Connection.
# Plan Configuration
After Fastly is enabled, open Configuration → Plans → DNS and expand CDN Configuration.
Select Fastly as the CDN provider and configure:
| Setting | Description |
|---|---|
| WAF | Enables Fastly Next-Gen WAF for the service (administrator-managed) |
| Force HTTPS | Redirects HTTP to HTTPS at the edge |
| Origin Shield | Adds an Origin Shield location in front of the origin |
| Shield Location | Shield POP (for example Amsterdam, Frankfurt, London, Newark, San Jose, Singapore, Tokyo, Sydney) |
| Under Attack Mode | Default under-attack state for new instances |
| Auto Purge on Update | Purges Fastly cache after WordPress content updates via the MU-plugin |
| Rate Limit (Normal / Attack) | Request limits applied by edge configuration |
| Cache TTL (HTML / Static) | Cache lifetimes for HTML and static assets |
Note: Fastly is a CDN provider, not a DNS server. Keep the plan DNS provider set to your existing DNS integration. PanelAlpha writes Fastly edge records into that DNS provider.
# How Provisioning Works
When an instance is created (or Fastly is attached to an existing site) on a plan with CDN = Fastly, PanelAlpha:
- Creates a Fastly service and configures the origin backend.
- Applies edge settings (VCL / dictionary), including cache rules for WordPress admin, login, and WooCommerce paths that must bypass cache.
- Provisions TLS and resolves the public DNS records Fastly expects.
- Syncs those records to the plan DNS provider so the apex points to Fastly anycast addresses instead of the origin IP.
- Attempts to enable WAF and install the CDN MU-plugin (best-effort steps that may log warnings if Fastly/WAF prerequisites are missing).
# Client Area Controls
Clients with the Manage CDN privilege can open Instance → Advanced → CDN when the plan CDN provider is Fastly and CDN is active for the instance.
Available actions:
- Purge Cache — purges the Fastly cache for the website
- Under Attack Mode — toggles the stronger edge protection profile
- Always-On Protection — read-only list of plan features visible to clients (for example Origin Shield, Auto purge on update)