Infrastructure Acceptable Use Policy (AUP)
Technical enforcement boundaries, prohibited plugin restrictions, automated deactivation protocols, and mandatory server hosting minimums.
WPSmooth guarantees world-class speed and edge security by enforcing strict boundaries between origin servers and edge proxies. Bloated local scanners and origin caching suites cause severe performance bottlenecks, database write contention, and cache synchronization loops. Origin environments must comply with these technical boundaries.
Prohibited Technology & Plugin Restrictions
-
✗Scope of Ban: The installation of bloated security suites (e.g., Wordfence) and comprehensive caching plugins (e.g., WP Rocket) is strictly prohibited on any managed site.Prohibited: Bloated Security SuitesWordfence, iThemes/Solid Security, Sucuri local scanners. Redundant with our Upstream Anycast Edge Shield; causes severe database bloat and disk I/O bottlenecks.Prohibited: Local Caching SuitesWP Rocket, W3 Total Cache, LiteSpeed Cache. Conflicts directly with dynamic edge caching, resulting in stale page rendering and cache sync loops.
-
✓Permitted Exceptions: No other specific plugin categories are explicitly banned, provided they do not interfere with the WPSmooth Client App API payloads or Anycast edge routing. Custom business plugins, form engines, WooCommerce, and synchronized asset optimizers are fully supported.
-
⚡Automated Enforcement: If a prohibited plugin is installed by the client, the automated Antigravity Python scripts will instantly command the WPSmooth Client App API to deactivate the offending plugin without prior warning. This ensures the proxy infrastructure remains uncompromised and origin stability is protected. Upon deactivation, an automated asynchronous ticket is instantly generated and dispatched to the client detailing the technical violation and remediation steps.
Mandatory Hosting Minimums (Infrastructure Baseline)
To ensure the reliable execution of the WPSmooth Client App REST API handshakes, isolated cloud vault backup streaming, and MU-plugin fatal error intercepts, all client server environments must meet the following strict minimums before the API connection is initialized:
PHP 8.1 or Higher
PHP 8.1+ required. PHP 8.3+ strongly recommended for optimal API processing speed, memory efficiency, and JIT compilation.
256MB PHP Memory
256MB minimum allocated strictly to PHP (memory_limit = 256M) to prevent fatal out-of-memory errors during API payloads or backup archive generation.
MySQL 8.0+ / MariaDB 10.4+
MySQL 8.0+ or MariaDB 10.4+ with full InnoDB transactional engine support and utf8mb4 collation compatibility.
60s Execution Runtime
Minimum PHP max_execution_time of 60 seconds to accommodate remote API operations and backup initiations without server-side termination.
Unrestricted REST API Access
Host-level firewalls or security modules (e.g., ModSecurity) must allow inbound REST API POST requests and must not aggressively cache the /wp-json/ endpoints. IP whitelisting may be required for strict environments.
Server-Level Cron
Standard WordPress cron (wp-cron.php) must be operational, or a server-level cron job must be configured to trigger every 5 minutes to ensure backup streaming reliability.
Have questions about your origin server compatibility?
Our engineering team can run an automated pre-flight scan of your origin server before initiating the onboarding handshake.