I started HarborCache for my own websites, with a focus on the dashboard, configuration and cache-management workflow I wanted to use. Redis Object Cache and Object Cache Pro were familiar products that I had used previously, so both naturally featured in the initial research and comparisons.
That is why OCP was mentioned: it was a feature reference during planning. HarborCache’s code foundation is the GPLv3 Redis Object Cache 3.0.0 release. The documentation identifies that origin and retains the upstream license and attribution. I have also removed unnecessary OCP comparisons from the current descriptions so HarborCache’s own features are clearer.
I chose a separate fork because the changes form a broader product direction: a different administration interface, local analytics, configuration controls, scoped invalidation and drop-in recovery. Maintaining those choices in HarborCache gives me room to develop and test them together for my sites.
Contributing upstream and maintaining a separate plugin can coexist. General fixes are candidates for upstream contribution, while HarborCache-specific interface and workflow decisions belong in this project. The intention is to develop a useful alternative with its own direction and clear attribution.
