WP Manifestindependent plugin directory
manifest / performance / harborcache

HarborCache – Object Cache with Redis

Redis object caching for WordPress with scoped invalidation, local analytics and cache diagnostics

by Shahid Irfan · github.com/shahidirfan100/harborcache

★ 0stars

Install

Download source zip No release zip yet

This is the repository archive. It installs, but the folder name will carry the branch suffix and updates will not flow.

Install straight from GitHub with WP-CLI:

wp plugin install https://github.com/shahidirfan100/harborcache/archive/refs/heads/main.zip
No built-in updater. New versions won't appear under Dashboard → Updates. Install new releases yourself, or let Git Updater track the repository.
Readme github.com/shahidirfan100/harborcache ↗

Persistent Redis object caching for WordPress, with scoped invalidation, connection management, sampled analytics, diagnostics and a dashboard statistics widget. Current release build: 1.2.7.

HarborCache brings connection settings, local analytics, scoped invalidation and recovery controls into one administration workflow. It was developed around the day-to-day needs of the author's websites and continues as a separate project with its own interface and development direction.

HarborCache

Install

Install the 1.2.7 ZIP on an isolated staging site under Plugins → Add New → Upload Plugin. GitHub's source archive includes development documentation and media; use the installable ZIP for WordPress.

Requires WordPress 6.6+, PHP 7.4+ and a separately operated Redis service. Disable the existing object cache manager through its own controls first. Configure a distinct prefix in Settings → HarborCache, save the connection and enable the object cache. HarborCache refuses to overwrite another plugin's drop-in. Verify connection status and Site Health before using it on production.

For upgrades, back up configuration and the owned drop-in. Upload the plugin, then update the HarborCache drop-in if prompted. Prefix ownership conflicts preserve the existing owner and use runtime-memory fallback; cloned sites should use a distinct prefix. See configuration, 1.2.7 release notes and acceptance gates.

Features

  • Predis, PhpRedis, Relay and Credis connection paths; standalone, replication, Sentinel and cluster configurations.
  • Multisite cache group scopes, typed values, bulk operations and bounded TTLs.
  • Namespace invalidation without FLUSHDB or FLUSHALL; bounded background reclamation.
  • Optional serialization/compression, split autoloaded options and registered-key prefetching.
  • Readable administration screens, equal-sized connection controls, responsive charts and accessible chart tables.
  • Local sampled request analytics, separate runtime/store counters, WP-CLI, Site Health, Query Monitor and Debug Bar support.
  • Protected configuration forms, redacted diagnostic exports, verified drop-in updates and recovery backups.

No license key or account is required. No plugin REST endpoints are included. Optional New Relic/OpenTelemetry adapters require explicit configuration and the host application's integration. See the feature ledger for supported behavior and validation boundaries.

Current screenshots

Overview

Dashboard statistics widget

All screenshots, logos, banners and favicons include version-free dashboard captures that remain reusable while the layout stays the same. They show a local test installation and demonstration chart history, not production speed measurements. Capture details are in screenshots.json.

Validation and deployment gates

The 1.2.7 release reuses key contexts, reduces bootstrap work and batches supported metadata commands while preserving ownership and critical-option safety. Dashboard assets remain unchanged; see 1.2.7 validation. Earlier release evidence remains in the versioned validation reports. Historical performance results in the comparison do not predict performance on every server or guarantee WordPress.org approval.

Sustained production load, native Relay topology/failover and production tracing agents remain acceptance gates. HarborCache does not claim WordPress.org approval or universal performance leadership. See acceptance gates.

Development direction

Experience using existing Redis caching plugins helped shape the initial requirements. HarborCache's development focuses on its own administration, configuration and cache-management choices. General fixes can be considered for upstream contribution alongside that work.

A separately developed engine is a future major-release proposal, with compatibility, migration and performance gates before any replacement. The independent-engine plan preserves the current dashboard and branding.

License and attribution

HarborCache is distributed under GPL-3.0-only. Its cache engine is a modified fork of Redis Object Cache 3.0.0 by Till Krüss and contributors. HarborCache's additional dashboard, configuration and cache-management work is by Shahid Irfan. Original notices and bundled dependency licenses are preserved; see LICENSE.md and source provenance. Original media has its separate GPL-2.0-or-later license described in media/README.md. Redis is a trademark of Redis Ltd.; no affiliation or endorsement is implied.