Skip to content
Hyperfluid 2.0 is live console.hyperfluid.cloud/signup
Redis-compatible cache

A Redis-compatible in-memory cache, created from the console.

A Redis-compatible in-memory cache, backed by Valkey

Provision an in-memory key-value cache directly from the console: backed by Valkey, it works with any Redis client and protocol, on your cluster's internal network. Managed credentials, built-in monitoring and GitOps deployment.

A Redis-compatible in-memory cache, created from the console.

Specifications

Engine
Valkey, Redis compatible
Sizes
128 MB to 4 GB
Connection
Internal redis:// URI
Eviction
8 policies

Use cases

Speed up your applications

Keep frequently accessed data in memory to ease the load on your database and cut response times, using your existing Redis libraries

Any Redis client and protocol

Handle temporary data

User sessions, lightweight queues, counters: an in-memory cache for your ephemeral data, reachable on the cluster's internal network

Internal redis:// URI

Rate-limit and count

Implement rate limiting, real-time counters or lightweight locks with Redis-compatible operations

8 eviction policies

In action

An application team speeds up its API

An API keeps reading the same data and needs to reduce the load on its database

  1. Create a cache instance from the console by picking a size preset
  2. Retrieve the redis:// connection URI from the secret manager
  3. Connect the application with a standard Redis library
  4. Cache the most frequently read data

Repeated reads are served from memory, database load is reduced

A platform team shares session state

A web application spread across several instances needs to share session state

  1. Provision a cache instance dedicated to sessions
  2. Pick a suitable eviction policy (allkeys-lru by default)
  3. Point the application instances at the internal endpoint
  4. Rotate the credentials from the console whenever needed

Session state shared across every instance, credentials managed in the secret manager

Key benefits

  • Backed by the open source Valkey engine: works with any Redis client and protocol, keeping your existing libraries
  • Self-service provisioning from the console, with no administrator
  • Managed credentials and one-click rotation, password never stored in clear text
  • Built-in monitoring, GitOps deployment and per-organization isolation

Ready to speed up your applications?

Provision a Redis-compatible key-value cache from your console and connect your applications with your existing libraries.