No. A cache plugin still leaves WordPress reachable and serves a cached copy faster. Static Shield generates a static release and can restrict which WordPress routes stay publicly reachable at all — a performance benefit plus deliberate route control, not just faster caching.
No. WordPress stays exactly where it is for content management and publishing. Static Shield changes how public requests are served, not how you manage content.
Yes. The Access & Isolation tab manages how admin access stays reachable — permanently via a trusted IP allowlist, or on demand via Vault Mode (Pro), which opens access for a limited window instead of leaving it open all the time.
Yes — Elementor has a coded compatibility profile. Its frontend output is served static; the editor itself stays behind admin authentication, since it was never part of the public surface to begin with. See the Elementor integration page for specifics.
Yes — WooCommerce has the most detailed compatibility profile of any integration. Product pages are served static; cart, checkout, and account stay dynamic, since they need real server-side state. WooCommerce is the clearest real-world case for Hybrid mode. See the WooCommerce integration page for the full breakdown.
It can likely still work. The integrations list only covers what's been specifically checked in code so far — it isn't the limit of what's compatible. Static Shield operates on ordinary rendered HTML, so most well-behaved themes and plugins that don't need a live PHP request for every page view are likely to work fine even without a dedicated profile of their own yet.
No. Static Shield works on standard hosting — it detects and configures for whichever webserver you're actually running (Apache, LiteSpeed, nginx, Caddy, or IIS).
Yes. There's no requirement for a specialized host or CDN — the Server Integration tab generates the matching configuration for your actual webserver.
Forms keep working through a narrow, purpose-built bridge route rather than requiring the whole page — or site — to stay dynamic. Contact Form 7 and WPForms both have coded compatibility profiles for this.
No — vulnerability and exposure are not the same thing. A vulnerable plugin remains vulnerable even when its known public attack path is isolated. Static Shield reduces what's reachable; updating or removing the vulnerable plugin is what actually fixes it.
It can reduce exposure, yes — but it's not a substitute for supported software, security updates, or migration planning. Isolation narrows the reachable window; it doesn't patch anything underneath it. This is especially relevant when an install genuinely can't be updated at all — stuck on an old host's PHP version, built on a theme or custom code nobody maintains anymore, or simply too risky to touch without a developer on hand. Static Shield itself runs in a reduced-feature Legacy Safe Mode down to PHP 7.0 and WordPress 5.2, so it doesn't require modernizing the install just to protect it — see "Protecting an outdated WordPress installation" for what that mode does and doesn't cover.
A Pro feature: default-deny for the public internet. Once active, any request that isn't a known static file, the Shield Bridge API, or a verified admin IP is denied outright, rather than being handed to WordPress. It can affect other plugins' AJAX, REST, or webhook endpoints, so it's worth reviewing your active plugins before turning it on.
A Pro feature that replaces standing wp-admin access with short-lived windows you open on demand — wake it when you need in, then let it expire automatically or close it manually, instead of leaving admin access reachable all the time.
Your static release keeps being served normally either way — serving static content doesn't depend on reaching Tulapp Cloud. Cloud-dependent Pro features (like remote monitoring) are naturally unavailable while the cloud is unreachable, but your site itself stays up.
Existing protection on an already-licensed site is never removed by a billing change — cancelling stops the subscription from renewing, it doesn't strip what's already applied. Pro-only features become unavailable going forward until the subscription is renewed.
Tulapp