Valkey and Memcached
Redis-protocol Valkey for caching, queues and sessions; Memcached for simple, fast caching.
Cache as a ServiceGA
Create Valkey or Memcached in seconds and connect it to an app or a WordPress site. WhyCloud measures the site before and after connecting and reports how much the cache helped.
HOW IT WORKS
Create Valkey or Memcached in the size you need.
Click “Connect cloud cache” on a WordPress site, or give the address to your app.
A few minutes later see the speed-up and the hit rate.
Capabilities
Redis-protocol Valkey for caching, queues and sessions; Memcached for simple, fast caching.
Nothing to fill in: WhyCloud creates a dedicated, secure cache on the site’s private network and connects it.
Time to first byte of the home page, search, REST API and shop before and after, plus the cache hit rate.
WooCommerce, Elementor, WPML, Yoast and membership plugins are detected, with what the object cache does for each.
Reachable only from the organization’s private network and apps; password and optional TLS.
In the WhyCloud cloud or on your connected servers, from the same console.
WORDPRESS
WordPress reads options, transients, product meta and widget data from the database dozens to hundreds of times per request. The object cache keeps those repeated reads in memory, and helps most on pages a page cache cannot serve (cart, account, search, admin).
FAQ
A page cache keeps whole HTML pages for anonymous visitors; an object cache keeps database results and also works for signed-in users, carts, search and the admin. They complement each other.
No. The WhyCloud drop-in silently falls back to normal WordPress behavior and never shows an error to visitors.
Sample pages are measured before connecting and again a few minutes after; the improvement, per-page bars and hit rate appear in the Speed tab.
Create an account and connect your first server in under five minutes.