Tier comparison

Free vs Pro

Free and Pro share the same cache engine. Pro extends that core with WooCommerce-aware behavior, optional logged-in caching, CDN integration, and external metrics exposure.

Shared Foundation

Both tiers are built on the same core cache engine.

  • Query caching for front-end WordPress query results
  • Fragment caching for expensive rendered sections
  • Redis as the preferred store, with MySQL fallback
  • Tag-based invalidation and per-site cache namespaces
  • Anonymous front-end caching on public pages
  • No full-page HTML cache
  • Designed to complement page caches and CDNs rather than replace them

This page is about capability and behavior. It does not include benchmark numbers.

QuantumCache Free vs Pro
Free provides the shared cache engine. Pro adds modules on top of it.
Capability / Behavior Free Pro
Core query cachingYesYes
Core fragment cachingYesYes
Redis storeYesYes
MySQL fallback storeYesYes
Admin controls for store mode, TTLs, debug headers, and purgesYesYes
WP-CLI commands for status and flushYesYes
Built-in lifetime hit/miss/store/purge countersYesYes
Anonymous public-page cachingYesYes
WooCommerce-aware cache key varianceNoYes
WooCommerce-specific fragment wrappersNoYes
WooCommerce bypass rules for cart, checkout, account, AJAX, and cart/session cookiesNoYes
WooCommerce invalidation on product, stock, order, review, term, and catalog-setting changesNoYes
Optional logged-in caching for allowlisted roles with a separate TTLNoYes
CDN cache-tag headers and purge integrationsNoYes
Prometheus scrape endpointNoYes
Pro-specific WP-CLI metrics commandNoYes
Full-page HTML cachingNoNo
Free vs Pro — Capability Structure (Pro extends Free)
DIAG-007: Free vs Pro — Capability Structure (Pro extends Free) QuantumCache Pro — extension layer (Pro only) Shared Engine (Free and Pro) Query Cache Stores DB query results Hit = DB call skipped · Measured: query_hits / query_misses Fragment Cache Stores rendered fragments Hit = rendering skipped · Measured: frag_hits / frag_misses Cache Stores Redis (primary) MySQL fallback when Redis unavailable Anonymous Public Page Caching Standard pages · WooCommerce archive and product pages as general content Pro-only behaviors — added on top of the shared engine above WooCommerce TTL Overrides X-QC-Pro-Force-TTL:90 on archive routes (assertion P3) Endpoint Bypass — br-001 /cart/ excluded from cache path X-QC-Pro-Obs-Bypass:1 reason:woo_endpoint (assertion P4 · source files document br-001 only) Product Invalidation InvalidationMap purges post_type:product on product update (assertion P5) Free does not implement WooCommerce invalidation Logged-in User Exclusion enable_logged_in_cache=0 → excluded before cache/bypass path (assertion P6) Behavior with =1 not documented No per-role differentiation documented Pro extends Free — it does not replace or reimplement it All Pro behaviors confirmed via capability assertions (perf_bench run_20260315_172849) Source: qc_source_of_truth.md §2, §3 Pro adds WooCommerce-specific correctness and control — not a raw speed increase Assertions: P3, P4, P5, P6, F3 Free does not expose or simulate any Pro behavior (assertion F3: Pro headers absent under Free on /shop/)

Pro extends the Free engine with additional modules. It does not replace or reimplement the core cache.

What Free Includes

Public WordPress caching

Free caches anonymous front-end requests with the shared query and fragment engine. It is aimed at public traffic and does not add logged-in caching.

Fragment coverage

Free automatically wraps the main post body in classic and block themes, query loops, excerpts, core navigation, latest posts, archives, and classic widget sidebars. On WooCommerce sites, those generic wrappers still apply where the output flows through the same WordPress hooks.

Configuration and operations

Free includes the main settings page, store selection (auto, redis, mysql), Redis connection fields, default query and fragment TTLs, minimum archive size, optional debug headers and HTML markers, and purge tools for everything, tags, or a resolved URL. It also includes wp quantumcache status and wp quantumcache flush.

WooCommerce boundary

Free can still cache WooCommerce pages as ordinary WordPress output, but it does not add WooCommerce-specific cache key separation, bypass rules, invalidation hooks, or role-scoped logged-in caching.

What Pro Adds

Pro extends the same engine with additional modules.

WooCommerce-aware cache keys

Pro separates WooCommerce catalog cache entries by the inputs that materially change catalog output: pagination, sort order, page size, search, layered navigation filters, rating and price filters, locale, selected currency, and geolocation variation state.

WooCommerce-specific fragment coverage

Pro adds dedicated wrappers for WooCommerce catalog fragments such as breadcrumbs, result counts, sorting controls, filter blocks, selected widgets, related products, product loops, and individual product cards.

Bypass rules for sensitive WooCommerce traffic

Pro bypasses cache access on cart, checkout, my-account, WooCommerce AJAX requests, non-GET/HEAD requests, and requests carrying WooCommerce cart or session cookies. It also applies a shorter WooCommerce archive query TTL.

Broader invalidation triggers

Pro adds WooCommerce purge hooks for product create, update, delete, and trash flows; stock changes; low-stock and no-stock events; order impact; completed-order status changes; review submissions; term cache and term lifecycle changes; and selected catalog options such as currency, tax display, out-of-stock visibility, and default customer address.

Optional logged-in caching

Pro can enable logged-in caching for selected roles, with a separate TTL and role allowlist. Sensitive routes such as cart, checkout, account, admin, AJAX, and REST requests remain out of scope.

CDN-aware headers and purge integrations

Pro can emit cache-tag and vary headers on responses and map tag purges to Cloudflare, Fastly, or LiteSpeed integrations.

Metrics exposure and operator tooling

Pro adds a Prometheus-compatible scrape endpoint with bearer-token protection, plus wp quantumcache pro:metrics for endpoint status, counters, and counter resets.

Decision Guide

This is a capability guide, not a performance claim.

Free

Free may be appropriate for:

  • WordPress sites without WooCommerce
  • WooCommerce sites where generic WordPress query and fragment caching is enough
  • Teams that want the core cache engine, admin controls, purge tools, and WP-CLI basics without WooCommerce-specific extensions
Pro

Pro may be appropriate for:

  • WooCommerce stores that need cache separation for filters, sorting, currency, locale, or geolocation
  • Stores that need broader invalidation when products, stock, reviews, orders, terms, or catalog options change
  • Sites that need limited logged-in caching for specific roles
  • Teams that want cache-tag headers, CDN purge integrations, or a Prometheus scrape endpoint

Continue into architecture and pricing

Request flow, implementation details, and tier information.