Skip to content
Ownkube

Cache (Valkey)

Ownkube provisions a managed Valkey cache in one click. Valkey is in-memory and Redis-compatible, so existing Redis clients connect unchanged. Choose Cache as the resource type, provisioned the same way as a database.

Use it for caching, sessions, rate limiting, and background or job queues.

Adding a cache

Section titled “Adding a cache”

  1. Choose Cache as the resource type

    From Create deployment, pick Cache instead of Database.

  2. Size it

    Pick a memory size from the cache box ladder. See Sizing below.

  3. Pick an environment

    Tag the cache to an environment like Development or Production.

  4. Create

    Ownkube provisions the cache and attaches connection details to the deployment as environment variables.

Sizing

Section titled “Sizing”

Pick a memory size from a ladder of cache boxes. A cache box always costs less than a database box of the same memory, since a cache carries no durable-volume line, there’s no storage charge. See Pricing for the current ladder.

Connecting your app

Section titled “Connecting your app”

When you attach a cache to a deployment, Ownkube injects the connection details as environment variables into your app container:

Terminal window
REDIS_URL=redis://:password@host:6379
REDIS_HOST=...
REDIS_PORT=6379
REDIS_PASSWORD=...

Any Redis-compatible client library connects with these values unchanged, no code changes needed.

Private by default

Section titled “Private by default”

A new cache has no public endpoint, reachable only from your own deployments over a private connection string. As with databases, a public edge is available as an opt-in for cases like connecting from a local tool, keep it off unless you need it. See Databases for how public access works on the same model.

Databases Managed PostgreSQL, provisioned and connected the same way.
Pricing Cache box sizes and rates.