Included on all plans

Know if your plugin will work on eight managed WordPress hosts

Every WP HealthKit audit scores your plugin against the specific restrictions and patterns that WP Engine, Kinsta, Flywheel, Cloudways, SiteGround, Pressable, GridPane & Rocket.net enforce. Incompatibilities are flagged with a per-host PASS / WARN / FAIL before you ship.

Check your plugin

Eight hosts. Eight sets of rules. One report.

Each managed host enforces its own restrictions. What passes on WP Engine may fail on Pressable. What works on GridPane breaks on Rocket.net. WP HealthKit checks all eight simultaneously.

WP Engine

Hosts 1.5M+ WordPress sites. One of the most comprehensive plugin restriction lists in managed hosting.

PHP session usage FAIL

Blocked entirely — use transients or user meta instead

Shell execution functions FAIL

Disabled at the OS level by ini config

File writes outside wp-content FAIL

Restricted to the wp-content directory tree

WP_CACHE constant modification FAIL

EverCache rejects plugin-level cache overrides

Aggressive cache flushing WARN

Flushing on every save defeats the page cache

Kinsta

Google Cloud infrastructure with Redis object cache as standard. Patterns that bypass the cache layer cause escalations.

Object cache bypass patterns WARN

Direct $wpdb reads that skip wp_cache_get/set reduce Redis effectiveness

Custom session handling FAIL

Multi-worker Nginx + PHP-FPM stack doesn't guarantee session persistence

Deprecated PHP functions WARN

Functions removed in PHP 8.x cause fatal errors

.htaccess modification FAIL

Nginx ignores .htaccess writes

Flywheel

Nginx-based infrastructure owned by WP Engine. Apache-specific server config silently no-ops.

.htaccess modification FAIL

Nginx — .htaccess writes have no effect

High-frequency cron WARN

Sub-15-minute intervals are throttled at the server level

Apache-specific rewrites FAIL

mod_rewrite rules do not translate to nginx

Cloudways

Multi-cloud platform (DigitalOcean, Vultr, Linode, AWS). Varnish full-page cache plus Breeze.

Aggressive cache flush hooks WARN

Wipes Varnish on every save_post — defeats the host cache

WP_CACHE constant overrides FAIL

Cloudways manages caching server-side via Varnish

Shell execution functions FAIL

Disabled across all Cloudways instances

.htaccess modification FAIL

Nginx — rewrites must run through WordPress hooks

SiteGround

Apache + SG Optimizer + Ultrafast PHP. Caching is server-side via SuperCacher; deprecated PHP fns are a runtime hazard.

Caching plugin interference WARN

Third-party cache plugins conflict with SG Optimizer

Object cache bypass WARN

Memcached + Redis available — bypassing reduces hit rate

Deprecated PHP functions WARN

Ultrafast PHP runs 8.1+ where ereg/split/mysql_* fatal

High-frequency cron WARN

External cron required for sub-15-minute schedules

Pressable

Owned by Automattic. Restrictions mirror WordPress.com VIP — the most restrictive managed-host profile in the market.

PHP sessions FAIL

Blocked — caching layer requires stateless responses

File writes outside wp-content FAIL

Restricted to wp-content/uploads only

Shell execution FAIL

Disabled at the PHP ini level

.htaccess modification FAIL

Nginx — .htaccess writes are silently dropped

Custom session handlers FAIL

Multi-worker stack drops session_set_save_handler

GridPane

Premium dev/agency platform. Nginx + Redis + 6G WAF. Users get real cron access; most server-level restrictions don't apply.

.htaccess modification FAIL

Nginx-only stack

Shell execution functions FAIL

Disabled in the default PHP-FPM pool

Object cache bypass WARN

Redis is standard — bypassing degrades the stack

File writes outside wp-content FAIL

PHP user runs unprivileged outside the WP tree

Rocket.net

Cloudflare Enterprise edge cache. Premium tier with aggressive page caching similar to WP Engine EverCache.

Aggressive cache flush hooks WARN

Wipes the Cloudflare edge on every save

PHP sessions FAIL

Blocked — sessions bypass the edge cache

WP_CACHE constant overrides FAIL

Edge cache is server-controlled, not plugin-controlled

.htaccess modification FAIL

Nginx origin — .htaccess ignored

Shell execution functions FAIL

Disabled across all plans

Why this matters before you ship

Managed hosting is where most WordPress sites live. WP Engine alone hosts 1.5M+ sites; Kinsta, SiteGround, Cloudways, and the others collectively host tens of millions more. Plugin banning is rare — but when it happens, your users see a “Plugin has been deactivated” notice with no warning, no explanation, and no rollback path.

Zero support tickets about broken installs on managed hosts
Confidence in your compatibility claim in plugin readme and marketing copy
Specific line-level feedback on which patterns cause failures
Catch issues during development, not after a 1-star review

WP EngineIncompatible

PHP sessions detected — blocked on this host

KinstaCompatible

PressableIncompatible

.htaccess modification — Automattic stack ignores it

CloudwaysCheck required

Aggressive cache flush hook detected — wipes Varnish on every save

Rocket.netCompatible

Where results appear in your report

Host compatibility is one layer inside the Layers tab of every audit report.

Layers tab

Host compatibility appears alongside the other 41 verification layers. Eight side-by-side cards, one per host, in a 4×2 grid.

Per-issue detail

Each WARN or FAIL lists the specific pattern detected, the affected file and line number, and a plain-English explanation.

Host reference links

Each host card links out to that host's homepage so you can sign up if needed. Compatibility scoring is independent of any affiliate relationship.

WP HealthKit may earn a commission if you sign up for hosting through our links. Our compatibility scoring is determined entirely by technical analysis and is not influenced by affiliate relationships.

Run a free compatibility check

2 tokens included, no card required. Upload your plugin ZIP or paste a WordPress.org slug.

Check your plugin