Help4 Net WordPress CDN, GeoDNS and WAF
| Path | Use it when | Next step |
|---|---|---|
| Free plugin | You want to install the WordPress connector and start plugin-managed onboarding | Download the plugin directly from Help4.net. |
| $8 Pro | One production domain needs Help4 DNS, GeoDNS, full proxy, WAF controls, broader POP reach, and stronger cache controls | Buy through the Help4 Network CDN catalog. |
| $20 Enterprise starting path | The full site needs managed GeoDNS proxy delivery, origin shielding, WAF policy, and advanced operational visibility | Request an Enterprise scope through Help4 Network. |
Why the layers matter
A CDN cache and a managed proxy solve different parts of delivery.
The WordPress plugin handles onboarding and sync. DNS and GeoDNS decide where traffic should go. Proxy and WAF controls inspect and protect requests before they reach the origin. The right plan depends on whether the goal is asset acceleration, production route control, or full-site protection.
Performance
Reduce unnecessary origin trips and use edge cache controls suited to the site.
GeoDNS
Steer requests using managed routing policy instead of relying on one fragile path.
WAF
Apply managed request controls and virtual-patching workflows ahead of WordPress.
Origin safety
Reduce direct exposure and keep controlled fallback behavior for full-proxy deployments.
Need the CDN path selected?
Start with the site and the problem, not a feature checklist.
Send the domain, current DNS/CDN, traffic regions, cache problem, security concern, ecommerce/login behavior, and whether nameserver changes are acceptable.