Managed Redis Hosting in the EU
In-memory cache for sessions, queues, and real-time features. Toggle it on and go.
- Latency
- < 1ms
- Memory
- Up to 10 GB
- Version
- Redis 7+
redis-cli -u $REDIS_URL --tlsSET session:8f2 "{...}" EX 900OK · 0.31 msGET session:8f2"{...}" · 0.24 mspersistence RDB+AOF · failover auto
Cached data and session tokens stay in eu-frankfurt
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 to cache queries and take read load off the database, or wire it into their web services for rate limiting and job queues. The free tier includes a 50 MB instance that runs for 30 days before it needs an upgrade.
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.
Pub/Sub Messaging
Built-in publish/subscribe messaging for real-time features, live notifications, and event-driven architectures.
Persistent Storage
Optional data persistence with RDB snapshots and AOF logging. Your data survives restarts and failovers.
TLS Encryption
All connections encrypted with TLS by default. Private networking available for services within Runsite.
Automatic Failover
Redis instances are automatically restarted on failure and rescheduled to healthy nodes with minimal downtime.
Data Structures
Full Redis data structure support: strings, hashes, lists, sets, sorted sets, streams, and HyperLogLog.
How Redis fits your stack
Redis sits between your application and database, reducing latency and offloading read traffic.
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.
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.
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.
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.
Get Started in Minutes
Simple integration with your existing tools and workflows.
# Add to your environment variables
REDIS_URL=redis://default:password@redis.runsite.app:6379
# With TLS
REDIS_URL=rediss://default:password@redis.runsite.app:6379Common 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.
Your Cached Data Stays in the EU
Hosted in Frankfurt, 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 Frankfurt, Germany 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. That makes Runsite a fit when you handle EU customer data or fall under the GDPR or the EU Digital Services Act.
Simple, transparent pricing
Pay only for the resources you actually use. Switch between monthly and hourly to see what you'll spend.
Sub-ms in-memory store
·Cache · Sessions · QueuesDrop-in Redis 7+ compatible store. Pub/Sub, automatic failover, TLS, RDB + AOF persistence.
Standard
≈ €0.0178/hour, billed hourly
Frequently Asked Questions
Common questions about this service.
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.
On paid plans, Redis data is persisted using RDB snapshots and AOF (Append Only File) logging. On the free plan, data is stored in memory only and will be lost on restart.
30 days from the day you create it. We email you before the deadline. On day 30 the instance stops accepting connections, and 7 days later it is deleted unless you upgrade to a paid plan, from €5/mo. Free Redis holds data in memory only and is not backed up, so export anything you want to keep before the instance stops. Paid instances have no time limit and keep RDB or AOF persistence across restarts.
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.
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.
Learn More About Redis
Hands-on articles from the Runsite blog.
Connection Pooling with PgBouncer: What Ports 5432 and 6432 Really Do
You 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.
ReadPostgreSQL "FATAL: sorry, too many clients already" — What It Means and How to Fix It
Your 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.
ReadWhat Are Cold Starts — and Why Your Free-Tier App Keeps Falling Asleep
Cold 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.
ReadYou Might Also Need
Services that work great together.
Web Services
Node.js, Python, Go, Ruby, Rust, or your own Dockerfile — Runsite builds it, runs it, and keeps it online on European infrastructure.
Learn morePostgreSQL
Managed PostgreSQL. Daily backups, one-click restore. Just connect and start querying.
Learn moreCron Jobs
Run scheduled tasks automatically. Set a schedule, we run your code — with logs and retries built in.
Learn moreYour app deserves to be online
Free to start. Deploy in under a minute. No credit card needed.