# Managed Redis — One-Click Cache & Data Store on Runsite

> Managed Redis-compatible caching on EU infrastructure: sessions, queues and Pub/Sub with RDB and AOF persistence, TLS and automatic failover. From €5/month.

1. [Home](/)
2. [Services](/services)
3. Redis

Data EU · Germany

# Managed Redis Hosting in the EU

In-memory cache for sessions, queues, and real-time features. Toggle it on and go.

[Start with €5 credit](https://dashboard.runsite.app/login)[Read the docs](https://docs.runsite.app/services/redis/)

Latency

< 1ms

Memory

Up to 10 GB

Version

Redis 7+

redis-cli — runsite

 redis 7

 redis-cli -u $REDIS_URL --tls

 SET session:8f2 "{...}" EX 900

 OK · 0.31 ms

 GET session:8f2

 "{...}" · 0.24 ms

 persistence RDB+AOF · failover auto 

Cached data and session tokens stay in Germany

Overview

Runsite Managed Redis is a one-click in-memory store for caching, sessions, queues, and real-time features. Toggle it on, copy the connection string, and you have a Redis 7+ instance with sub-millisecond latency and TLS on by default.

Instances run inside the European Union, so cached data and user sessions stay within EU borders. A signed GDPR Data Processing Agreement is included on every plan.

You get the full Redis data-structure set, Pub/Sub messaging, optional RDB and AOF persistence, and automatic failover. Most teams run it next to [managed PostgreSQL](/services/postgresql) to cache queries and take read load off the database, or wire it into their [web services](/services/web-services) for rate limiting and job queues. Redis starts at €5/mo for 256 MB, which is what the €5 credit on a new account covers if Redis is the only thing you run.

Last reviewed: September 2026

At a glance

Latency

< 1ms

Memory

Up to 10 GB

Version

Redis 7+

Persistence

RDB + AOF

Encryption

TLS default

Failover

Automatic

Hosted in the EU · Germany

[Start with €5 credit](https://dashboard.runsite.app/login)

Features

## Everything You Need from Managed Redis

Built-in tools and capabilities to deploy and manage with confidence.

### Sub-Millisecond Latency

In-memory data access with sub-millisecond response times. Ideal for caching, session storage, and real-time leaderboards.

The number is real and rarely the reason to add a cache. A cache pays for itself when the same key is read repeatedly and the source query is genuinely expensive; if writes outnumber reads, the second copy adds invalidation and memory cost for almost no benefit.

### Pub/Sub Messaging

Built-in publish/subscribe messaging for real-time features, live notifications, and event-driven architectures.

Publish and subscribe with no persistence: a message goes to the subscribers connected at that moment and to nobody else. That makes it right for live notifications and log streaming, and wrong for a job queue, where a subscriber that was restarting must still get the work.

### Persistent Storage

Optional data persistence with RDB snapshots and AOF logging. Your data survives restarts and failovers.

RDB snapshots and AOF logging are both enabled, so an instance survives a restart with its data. That matters most for the things people keep in Redis that exist nowhere else — sessions, queue state, rate-limiter counters — which a pure cache configuration would happily throw away.

### TLS Encryption

All connections encrypted with TLS by default. Private networking available for services within Runsite.

Connections are encrypted by default, and services inside Runsite can also reach the instance over private networking. Neither removes the harder question, which is what the instance holds: sessions and rate-limiter counters are personal data, and they sit in your backups as long as the retention window.

### Automatic Failover

Redis instances are automatically restarted on failure and rescheduled to healthy nodes with minimal downtime.

A failed instance is restarted and rescheduled onto a healthy node. A restart is not free even so: connections drop and have to be re-established, so application code needs a retry around the first call after one rather than treating a cache read as infallible.

### Data Structures

Full Redis data structure support: strings, hashes, lists, sets, sorted sets, streams, and HyperLogLog.

Strings, hashes, lists, sets, sorted sets, streams and HyperLogLog, which is the difference between Redis and a plain key-value cache. Sorted sets are what make a sliding-window rate limiter possible in a few commands; streams are what make a durable queue possible without adding a broker.

Caching Pattern

## How Redis fits your stack

Redis sits between your application and database, reducing latency and offloading read traffic.

1

### App Checks Cache First

Your application queries Redis before hitting the database. Cache hits return data in sub-millisecond time, avoiding expensive database queries entirely.

2

### Cache Miss → Database Query

On a cache miss, your app queries PostgreSQL, stores the result in Redis with a TTL (time-to-live), and returns it to the user. Subsequent requests are served from cache.

3

### Real-Time Features via Pub/Sub

Use Redis Pub/Sub channels for live notifications, chat messages, or presence indicators. Multiple web service instances subscribe to the same channel for consistent real-time behavior.

4

### Session & Queue Management

Store user sessions with automatic expiration across all your service instances. Use Redis lists as lightweight job queues for background processing without a separate queue service.

Code

## Get Started in Minutes

Simple integration with your existing tools and workflows.

connection.sh

```
# Add to your environment variables
REDIS_URL=redis://default:password@redis.runsite.app:6379

# With TLS
REDIS_URL=rediss://default:password@redis.runsite.app:6379
```

Use Cases

## Common Redis Workloads

Common scenarios where this service shines.

### Application Caching

Cache database queries, API responses, and computed results to reduce latency and database load.

### Session Management

Store user sessions with automatic expiration. Share sessions across multiple web service instances.

### Real-Time Features

Build live dashboards, chat applications, presence indicators, and real-time notifications with Pub/Sub.

### Rate Limiting & Queues

Implement API rate limiting, job queues, and task scheduling with Redis lists and sorted sets.

EU-Sovereign

## Your Cached Data Stays in the EU

Hosted in Germany — your data stays under EU jurisdiction.

Your Redis instance, the keys you cache, user sessions, and any RDB or AOF persistence files run in Runsite's German region. Cached personal data and session tokens never leave the EU.

Every account is GDPR-compliant by default and includes a signed Data Processing Agreement at no extra cost and with no sales call. You can review how we handle data in our [Privacy Policy and DPA terms](/privacy). That makes Runsite a fit when you handle EU customer data or fall under the GDPR or the EU Digital Services Act.

EU data residencyGDPR-readySigned DPA on every plan

Pricing

## Simple, transparent pricing

Pay only for the resources you actually use. Switch between monthly and hourly to see what you'll spend.

Runsite is in Public Beta

Every service listed here is live, and paid plans bill exactly as shown. Beta means the platform is young. Features still change, and parts of the roadmap are not built yet.

### Long-running web servers

·Apps · APIs · Backends

Push your repo, Runsite builds and serves. Auto-scale, zero-downtime rolling deploys, free SSL.

Web Services

### Nano

€3/mo

≈ €0.0041/hour, billed hourly

vCPU

0.1

RAM

256 MB

Disk

1 GB

Bandwidth

100 GB

[Choose Nano](https://dashboard.runsite.app/login)

Web Services

### Starter

€5/mo

≈ €0.0068/hour, billed hourly

vCPU

0.5

RAM

512 MB

Disk

5 GB

Bandwidth

1 TB

[Choose Starter](https://dashboard.runsite.app/login)

Web Services

### Standard

Popular

€12/mo

≈ €0.0164/hour, billed hourly

vCPU

1

RAM

1 GB

Disk

10 GB

Bandwidth

2 TB

[Choose Standard](https://dashboard.runsite.app/login)

Web Services

### Pro

€25/mo

≈ €0.0342/hour, billed hourly

vCPU

1

RAM

2 GB

Disk

10 GB

Bandwidth

5 TB

[Choose Pro](https://dashboard.runsite.app/login)

Web Services

### Pro Plus

€50/mo

≈ €0.0685/hour, billed hourly

vCPU

2

RAM

4 GB

Disk

20 GB

Bandwidth

10 TB

[Choose Pro Plus](https://dashboard.runsite.app/login)

Web Services

### Business

€95/mo

≈ €0.1301/hour, billed hourly

vCPU

4

RAM

8 GB

Disk

20 GB

Bandwidth

20 TB

[Choose Business](https://dashboard.runsite.app/login)

Web Services

### Business Plus

€180/mo

≈ €0.2466/hour, billed hourly

vCPU

8

RAM

16 GB

Disk

30 GB

Bandwidth

30 TB

[Choose Business Plus](https://dashboard.runsite.app/login)

Nano is the entry plan: the same 0.1 vCPU / 256 MB as before, now €3/mo and covered by your €5 starting credit. Nano services draw on a 100 GB monthly egress pool, ship a noindex header, and sleep after 14 days with no traffic. Starter and above are always-on, indexable and unmetered on egress.

### JAMstack & static frontends

·Landing pages · Docs · Portfolios

Deploy Next.js, Astro, Vite, Hugo and friends to a global CDN. Auto-deploy from Git, preview on every PR, free SSL.

Static Sites

### Free

Popular

Free

Never billed · never draws on your balance

CDN

Global

Bandwidth

100 GB

Builds

\~20s

Sites

Unlimited

[Deploy for free](https://dashboard.runsite.app/login)

Static sites are not billed. No plan, no hourly charge, and they never draw on your balance or credit. Pay-as-you-go bandwidth above the included quota will be introduced after launch. We'll notify you before any change.

### Production-ready databases

·Managed · Backups · EU-sovereign

One-click PostgreSQL with daily backups, connection pooling, encrypted at rest, never leaves the EU.

PostgreSQL

### Nano

€3/mo

≈ €0.0041/hour, billed hourly

vCPU

0.1

RAM

256 MB

Storage

1 GB

Connections

25

[Choose Nano](https://dashboard.runsite.app/login)

PostgreSQL

### Starter

€5/mo

≈ €0.0068/hour, billed hourly

vCPU

0.5

RAM

1 GB

Storage

5 GB

Connections

50

[Choose Starter](https://dashboard.runsite.app/login)

PostgreSQL

### Standard

Popular

€14/mo

≈ €0.0192/hour, billed hourly

vCPU

1

RAM

2 GB

Storage

10 GB

Connections

100

[Choose Standard](https://dashboard.runsite.app/login)

PostgreSQL

### Pro

€35/mo

≈ €0.0479/hour, billed hourly

vCPU

2

RAM

4 GB

Storage

20 GB

Connections

200

[Choose Pro](https://dashboard.runsite.app/login)

PostgreSQL

### Pro Plus

€70/mo

≈ €0.0959/hour, billed hourly

vCPU

4

RAM

8 GB

Storage

50 GB

Connections

400

[Choose Pro Plus](https://dashboard.runsite.app/login)

PostgreSQL

### Business

€130/mo

≈ €0.1781/hour, billed hourly

vCPU

8

RAM

16 GB

Storage

100 GB

Connections

500

[Choose Business](https://dashboard.runsite.app/login)

Storage beyond the included quota: +€0.25/GB/mo. Daily encrypted backups included. Nano is the entry plan at €3/mo. There is no longer a 30-day free database. If your credit and balance run out the database stops with its volume intact; press Start after topping up and it comes straight back. Storage is reclaimed 7 days later and the final backup is kept for 12 months.

### Sub-ms in-memory store

·Cache · Sessions · Queues

Drop-in Redis 7+ compatible store. Pub/Sub, automatic failover, TLS, RDB + AOF persistence.

Redis-compatible

### Starter

€5/mo

≈ €0.0068/hour, billed hourly

Memory

256 MB

Connections

250

[Choose Starter](https://dashboard.runsite.app/login)

Redis-compatible

### Standard

Popular

€13/mo

≈ €0.0178/hour, billed hourly

Memory

1 GB

Connections

1,000

[Choose Standard](https://dashboard.runsite.app/login)

Redis-compatible

### Plus

€25/mo

≈ €0.0342/hour, billed hourly

Memory

2 GB

Connections

2,000

[Choose Plus](https://dashboard.runsite.app/login)

Redis-compatible

### Pro

€65/mo

≈ €0.0890/hour, billed hourly

Memory

5 GB

Connections

5,000

[Choose Pro](https://dashboard.runsite.app/login)

Redis-compatible

### Max

€125/mo

≈ €0.1712/hour, billed hourly

Memory

10 GB

Connections

10,000

[Choose Max](https://dashboard.runsite.app/login)

Redis starts at Starter. The 50 MB free instance is no longer offered. Every plan here includes RDB + AOF persistence, TLS and automatic failover, and is billed by the hour like everything else. A Starter instance runs for roughly a month on the €5 starting credit, if it is the only thing you have running.

Runsite hosts applications, not relays. VPN endpoints, proxies, VLESS / Xray / V2Ray and Shadowsocks nodes, and traffic tunnels of any kind are prohibited on every plan, paid ones included, and are blocked without notice or refund. See the Acceptable Use Policy in Section 4 of the Terms.

### Every plan, side by side

__Redis-compatible plans, with monthly and hourly prices in euro__
| Plan     | Memory | Connections | Per month | Per hour |
| -------- | ------ | ----------- | --------- | -------- |
| Starter  | 256 MB | 250         | €5        | €0.0068  |
| Standard | 1 GB   | 1,000       | €13       | €0.0178  |
| Plus     | 2 GB   | 2,000       | €25       | €0.0342  |
| Pro      | 5 GB   | 5,000       | €65       | €0.089   |
| Max      | 10 GB  | 10,000      | €125      | €0.1712  |

[Compare all plans](/pricing)[Try the calculator](/pricing/calculator)

FAQ

## Frequently Asked Questions

Common questions about this service.

### Which Redis version is supported?

Runsite runs Redis 7+ which includes all modern features: Redis Functions, client-side caching, ACLv2, and improved memory efficiency. We upgrade to the latest stable release automatically.

### Is data persisted across restarts?

Redis data is persisted using RDB snapshots and AOF (Append Only File) logging on every plan. Snapshots survive restarts and failovers, so a cache warmed over days is not lost the first time an instance moves.

### Is there a free Redis plan?

No. The 50 MB free instance is no longer offered — Redis starts at Starter, €5/mo for 256 MB, billed by the hour like everything else. The €5 of credit on a new account covers roughly a month of it, if it is the only service you have running. Instances created on the old free plan keep running until their owner deletes them, but the plan cannot be selected for anything new. If your credit and balance run out, the instance stops. Redis is in-memory and is not backed up, so export anything you want to keep before that happens — a Postgres database in the same situation keeps its volume, Redis does not.

### Can I use Redis as a primary database?

While Redis supports persistence, it is optimized for caching and in-memory workloads. For primary data storage, we recommend PostgreSQL. Redis is best used alongside PostgreSQL for caching, sessions, and real-time features.

### How do I connect from my web service?

Add the REDIS\_URL environment variable to your web service. Runsite provides both internal (private network) and external connection strings. Internal connections are faster and free of charge.

Guides

## Learn More About Redis

Hands-on articles from the Runsite blog.

[Caching12 min readWhen to Use Redis as a Cache (and When It Makes Things Worse)A cache is a second copy of your data that is allowed to be wrong. This is the decision frame: what to cache, what never to, the four failures that only appear in production, and why a cache full of sessions is a compliance object.Read](/blog/when-to-use-redis-cache)[Databases10 min readConnection Pooling with PgBouncer: What Ports 5432 and 6432 Really DoYou switched to port 6432 to stop the connection errors, and now prepared statements throw and SET doesn't stick. That's pooling working as designed. Here's what a pooler actually does, why 5432 and 6432 are different contracts, and what breaks in transaction mode.Read](/blog/pgbouncer-connection-pooling)[Databases10 min readPostgreSQL "FATAL: sorry, too many clients already" — What It Means and How to Fix ItYour app is suddenly throwing 500s and the database logs are full of "too many clients already." Here's what the error really means, how to see what's hogging your connections, and the fix that actually holds: pooling, not a bigger number.Read](/blog/postgres-too-many-clients-already)[Deployment7 min readWhat Are Cold Starts — and Why Your Free-Tier App Keeps Falling AsleepCold starts make the first request to a sleeping app painfully slow. Here's why free hosting tiers spin down, what it costs you, and how to keep an app warm without paying for idle capacity.Read](/blog/cold-starts)

Related

## You Might Also Need

Services that work great together.

[Web ServicesNode.js, Python, Go, Ruby, Rust, or your own Dockerfile — Runsite builds it, runs it, and keeps it online on European infrastructure.Learn more](/services/web-services)[PostgreSQLManaged PostgreSQL. Daily backups, one-click restore. Just connect and start querying.Learn more](/services/postgresql)[Cron JobsRun scheduled tasks automatically. Set a schedule, we run your code — with logs and retries built in.Learn more](/services/cron-jobs)

## Your app deserves to be online

€5 of credit on signup. Deploy in under a minute. No credit card needed.

[Start deploying](https://dashboard.runsite.app/login)[View documentation](https://docs.runsite.app)

---

Source: https://runsite.app/services/redis