Redis

Available

Runsite Platform provides fully managed Redis — for caching, session storage, queues and pub/sub. Provisioned in seconds, with TLS on the public endpoint and zero exposure on the internal one.

Supported versions

Redis 6, 7 (default) and 8.

Creating an instance

POST /api/redis
Content-Type: application/json

{
  "name": "session-cache",
  "redis_version": "7"
}

The response includes the password and both connection URLs.

Connection URLs

Each Redis instance exposes two endpoints:

URL	When to use it
Internal	From other Runsite services in the same project. Stays on the private network.
External	From anywhere on the internet. Encrypted with TLS.

Both URLs are standard Redis connection strings:

redis://:password@host:6379
rediss://:password@host:6379   # TLS variant for the external URL

From a Runsite Web Service

REDIS_URL=redis://:password@redis-internal.runsite.local:6379

Set it in your web service’s environment variables and use it from any Redis client.

From your laptop

redis-cli -u "rediss://:password@redis.runsite.app:6379"

Lifecycle

Operation	Endpoint
Start	POST /api/redis/{id}/start
Stop	POST /api/redis/{id}/stop
Status	GET /api/redis/{id}/status
Update	PATCH /api/redis/{id}
Delete	DELETE /api/redis/{id}

Stopping an instance releases its compute. Data is preserved (subject to the persistence configuration) and available when you start it again.

Memory

Each instance has a memory limit configured at creation time. Resize up at any moment without downtime.

Metrics & logs

Endpoint	Description
GET /api/redis/{id}/metrics	Current CPU, memory and connection count.
GET /api/redis/{id}/metrics/history?period=3600	Historical metrics.
GET /api/redis/{id}/logs?tail=100	Recent server logs.
WS /api/redis/{id}/logs/stream	Live log stream.

Persistence

Redis instances persist data to disk by default. You can disable persistence for ephemeral cache use cases on the instance settings page.

Backups

Manual snapshots and scheduled snapshots are available. See Backups.

Use the right URL

Always prefer the internal URL when connecting from another Runsite service — it is faster, free of egress, and never exposed publicly. Reserve the external URL for local development and tooling outside Runsite.