LSCache control
Stamps X-LiteSpeed-Cache-Control and tag headers so a LiteSpeed server serves whole pages without touching PHP or MySQL. If the third-party LiteSpeed Cache plugin is present, page caching is deferred to it — no conflict.
Zinn plugins
Free plugins on every Zinn Digital site
Every WordPress site we host ships with two Zinn Digital® plugins, pre-installed and kept up to date for you: Zinn Cache for server-side full-page and object caching, and Zinn Footprint for a cleaner, more generic site fingerprint. Both are built to WordPress.org directory standards, translated into 58 languages, licensed GPL-2.0-or-later, and free.
- 58languages, translation-ready
- GPL-2.0+open licence, no lock-in
- 100,000+PBN sites hosted across every niche
Two plugins, no admin, no cost
We wrote these plugins to run our own hosting fleet — more than 100,000 PBN sites across every niche — so they are built for scale, security and performance, not as add-ons to upsell. They come switched on when your site is provisioned, and the worker agent keeps the files current: on a new release the plugin is redeployed and re-activated for you, so you never click update.
Both are repo-grade: they meet the WordPress Coding Standards, pass security review, raise no PHP notices, and degrade gracefully where a capability is absent. Because they are GPL-2.0-or-later there is no lock-in — you keep working plugins whether or not you stay with us.
Zinn Cache — server-side caching and smart purge
Full-page caching at the web-server layer, an optional Redis object cache, and purges that only clear what actually changed.
Smart tag-based auto-purge
When a post, comment, term, theme or plugin changes, only the affected pages and their listings are purged via targeted cache tags — not the whole site. Purges mirror to the panel over a signed webhook so the CDN edge clears in step.
Redis object cache
A one-click toggle installs a self-contained object-cache drop-in that offloads repeated database reads. It never overwrites another plugin's drop-in, and falls back to an in-memory cache if Redis is unreachable, so the site keeps working.
Safe cache exclusions
Sensible WordPress, WooCommerce and Easy Digital Downloads defaults — cart, checkout, my-account, REST/AJAX, preview, search and any logged-in or session request are never cached. Add your own path, query and cookie rules per site.
Signed remote purge
A REST endpoint lets the control plane purge everything, specific URLs or specific tags, authenticated by an administrator or an HMAC-SHA256 signature over the request body — reading only the signed payload, never query params.
Graceful degradation
Full-page caching needs a LiteSpeed server; without one the plugin simply emits no cache headers while the object cache, exclusions API and remote purge all keep working. Caching is a per-blueprint capability, not an all-or-nothing switch.
Zinn Footprint — a smaller WordPress fingerprint
Removes the tell-tale signals that reveal a site is running WordPress, and which version. Every measure is an independent toggle, so any can be turned off if a theme or plugin depends on it.
- Removes the generator meta tag from the page head and feeds.
- Strips the WordPress version from asset URLs — but only when the ?ver value equals the core version, so custom cache-busting versions are preserved.
- Removes RSD, Windows Live Writer, shortlink and REST/oEmbed discovery links.
- Disables XML-RPC, a common fingerprint and attack surface.
- Disables pingbacks, dropping the pingback methods and the X-Pingback header.
- Hides login error detail behind a single generic message instead of confirming which of the username or password was wrong.
- Removes the X-Powered-By header where PHP allows it.
How they reach your site and stay current
- Deploy-push is the primary path: the worker agent lays the plugin files into each site as part of the deploy footprint and redeploys them on every release — an idempotent overwrite that also keeps the plugin active.
- An in-plugin self-hosted updater is the belt-and-braces layer, force-enabling WordPress auto-updates so the admin reflects the right version even if a fleet push lags.
- Updates are pulled over HTTPS from our control plane, HMAC-authenticated in both directions, with the package host restricted and a SHA-256 checksum verified before install — a tampered download is refused.
- Per-site secrets are injected from Vault at provision time and never committed; every feature is inert without its constants, so the plugins also run standalone.
FAQ
Do the plugins cost anything?
No. Zinn Cache and Zinn Footprint are free and ship pre-installed on every WordPress site we host. They are licensed GPL-2.0-or-later, so there is nothing to buy and no lock-in.
Does Zinn Cache require a LiteSpeed server?
Full-page caching does — it uses the LiteSpeed (LSCache) module or the third-party LiteSpeed Cache plugin. On other servers the plugin simply emits no cache headers, while the Redis object cache, the exclusions API and remote purge all continue to work.
What happens if Redis is unavailable?
The object cache is optional. If the phpredis extension is missing the toggle is disabled with a notice, and if Redis becomes unreachable at runtime the drop-in serves from a per-request in-memory cache, so the site never breaks.
Will Zinn Footprint break my site?
The defaults are safe for typical sites, and every measure is an independent toggle. If an integration relies on XML-RPC — the WordPress mobile app or Jetpack, for example — or on discovery links, you can turn that one measure off.
Do I have to manage or update them?
No. The worker agent keeps the files current on every release and the in-plugin updater force-enables auto-updates, so no one ever has to click update. Updates are signed and checksum-verified before they install.
Related
Get both plugins on your first site
Start a card-free 7-day trial and your site is provisioned with Zinn Cache and Zinn Footprint switched on. Free migrations, a 30-day money-back guarantee and a 99.99% uptime assurance, with no vendor lock-in.
Start free