Redis hosting
Redis hosting,
on a server you control.Add Redis to your project in one click and run it on a server we provision and maintain. It sits right next to your app for low-latency caching, queues, and sessions, with no Redis server to install, secure, or patch yourself.
Why rent a VPS just to run redis-server, when you can SelfHost it?
How it works
Redis, one click away.
Inside a server you control.
On Selfhost.dev, Redis runs as a one-click database inside a Project, a managed server, alongside the app that uses it. You do not stand up a Redis server or wire up a separate host: create a project, add Redis, and read the connection string from your app. We run the box; you use Redis.
In 5 steps
One click to a database.
No server to set up.
From zero to a running Redis in a few clicks, with the server handled for you.
Create a Project
Give it a name and Selfhost.dev provisions a dedicated server for you in a couple of minutes.
Add Redis in one click
From the add-service screen, pick Redis. It comes up inside your project, ready to use.
Read the connection string
Copy the Redis URL from the project and set it as REDIS_URL (or your client config) in your app service.
Deploy your app beside it
Run your API or worker in the same project, so app and cache share one server with low latency.
Watch it live
Live CPU, memory, and connection metrics for the project, with logs, all in one place.
What it is good for
Redis, where it fits.
Cache database queries, API responses, and rendered fragments to cut latency and load.
Back BullMQ, Sidekiq, Celery, or RQ with Redis for background jobs, in the same project as your worker.
Store sessions and token buckets in Redis for fast, shared state across your app instances.
Use Redis pub/sub for lightweight realtime messaging between your services.
What you get
Redis, the easy way.
On a server you control.
No apt install, no config file, no systemd. Redis is added to your project and runs on a server we maintain.
App and Redis share one project server, so calls stay on the same box and latency stays low.
Live metrics and logs on a dedicated server you control, not a shared black box.
Billed with the project server by the hour, from around $0.02/hr, paused at a zero balance.
Add Redis, manage the project, and check metrics from Claude, Cursor, or any MCP client with 150+ MCP tools.
Redis runs on your project server with your other services, not a multi-tenant cache you cannot see.
Two ways to run Redis
Redis 7.0 or 7.2 with automated backups, snapshots, read replicas, encryption at rest, and live metrics with alerts. Best for a production cache or queue you want isolated on its own hardware.
Deploy managed RedisRedis added to a server we run, right next to your app. Best when your app just needs Redis beside its code.
Add Redis to a projectRelated guides.
Measured on the managed instance
The managed instance is fast, and benchmarked in the open.
The other way to run Redis here, the fully-managed dedicated instance on AWS, benchmarks at up to 230k ops per second with a 0.88 ms P99 on a single connection, on one r7g.large. We publish the full latency percentiles and the exact method, nothing cherry-picked.
See the Redis benchmarks