Redis

Available

Runsite runs Valkey, the open-source fork of Redis. It speaks the same protocol, so any Redis client, library or redis-cli works unchanged. The dashboard labels these instances Valkey.

This page documents how an instance behaves on Runsite: versions, persistence, lifecycle and the two endpoints it exposes. Typical uses are caching, session storage, queues, rate limiting and pub/sub. The public endpoint is TLS-encrypted; the internal one never leaves the platform.

Looking for plans or pricing?

Plans, memory sizes, free-tier limits and pricing are not documented here. They live on the managed Redis hosting page. This section covers how the instance works once it is running.

Supported versions

Version	Notes
7.2	Default. Recommended for new instances.
8.0	Latest.

Pick the version when you create the instance. It can’t be changed later.

Creating an instance

From the dashboard: pick a project, choose the major version and the memory plan, hit create. Provisioning takes a few seconds.

When the instance is ready, the Overview tab shows both connection URLs with the password masked. Click the eye icon to reveal it at any time. The password can’t be changed, so if it leaks, create a new instance and switch your app to it.

Memory and persistence

Memory comes from the plan. You can move between paid plans in Settings → Plan; the instance restarts briefly to apply the new limit.

Plans come in two kinds:

• Persistent plans keep data on a disk. It survives restarts, stops and plan changes.
• Cache plans keep data in memory only. Anything stored is lost when the instance restarts or stops.

You can’t switch between a persistent and a cache plan, because they use different storage. Create a new instance instead.

Redis doesn’t evict keys by itself here. When the dataset outgrows the plan’s memory, the instance restarts. See Fix Redis connection and memory errors for how to set TTLs or an eviction policy.

Lifecycle

Action	What it does
Start	Bring a stopped instance back online.
Stop	Shut the instance down. Compute is released. Data is kept on persistent plans and lost on cache plans.
Delete	Remove the instance permanently. There is no undo, so make a backup first.

FAQ

Can I change the Redis version or memory size after creating the instance?

The version is fixed. Memory can change: switch to another paid plan in Settings → Plan. The one thing you can’t do is move between a persistent and a cache plan.

Should I use the internal or external connection URL?

Use the internal URL from other Runsite services in the same project; it’s faster and stays off the public internet. Use the external URL, which is TLS-encrypted, from anywhere else. See Connecting.

Is my data kept when I stop the instance?

On persistent plans, yes. Click Start and the data is still there. Cache plans keep everything in memory, so stopping or restarting them empties the instance.

I lost my Redis password, can I get it back?

Yes. Open the instance’s Overview tab and click the eye icon next to either connection URL. The password can’t be changed, though, so if it leaked, create a new instance.

Can I use Redis as a primary database?

Redis is in-memory and best for caching, sessions, queues, rate limiting and pub/sub. For durable relational data, use PostgreSQL instead.

Where to next

• Connecting compares the internal and external URLs and shows how to use each.
• Dashboard walks through what each tab does.
• Backups covers daily and on-demand snapshots and restore.
• Troubleshooting covers NOAUTH, TLS and out-of-memory restarts.

Need a relational database?

If your data is rows and tables instead of keys and values, use PostgreSQL instead.