Serverless Redis
A real Redis endpoint in seconds. Free tier, TLS by default, the same redis-cli reflexes you already have. Cloud, desktop, or self-host.
Keys
- session:847STR
- user:1247HASH
- cart:1247LIST
- leaderboardZSET
Where to run it
Cloud, desktop, or self-host
One database, three places it can live. Pick the speed you want and move between them when you outgrow it.
What you get
Production features, free tier included
Every Redis database ships with the same primitives: TLS, web console, hibernation, and a real dashboard. No tiered features hidden behind a sales call.
Web IDE
Query console in the dashboard, no extra client to install.
TLS by default
All connections encrypted. No setup required.
Always-on connections
Optional keep-alive add-on prevents hibernation.
Scale to zero
Hibernates when idle. Wakes on the next connection.
Connection pooling
Pooled endpoint for serverless and edge workloads.
Direct connections
Bypass the pooler for migrations and replication.
HTTPS access
HTTP-native engines reachable over port 443.
Serverless driver
Upstash REST or PlanetScale serverless drivers supported.
IP whitelisting
Restrict access to specific IPs or CIDR ranges.
Automatic backups
Scheduled point-in-time backups with one-click restore.
Quick start
Connect with any Redis client
Session stores, caches, rate limiters, pub/sub, queues, and anything that fits a key/value or sorted-set shape.
- Drop a Redis cache in front of your database without managing a node
- Per-tenant session stores that scale to zero between bursts
- Rate limiting and feature flags at the edge with the serverless driver
- Real-time leaderboards and pub/sub for prototypes that go to production
- Self-host on your own hardware with SpinDB when compliance requires it
redis-cli -u "rediss://default:password@your-host.cloud.layerbase.dev:6379" pingSibling engine
Or try Valkey, Redis-protocol-compatible and license-clean
Valkey is the Linux Foundation fork of Redis that speaks the same wire protocol without the BSL/SSPL license complications. For new projects, point your client at Valkey instead: same redis-cli, same drivers, same commands.
Questions
Common Redis questions
Which Redis version do you run?+
Layerbase Cloud runs a Redis version from before the BSL/SSPL license transition, so existing Redis clients work unchanged. For new projects we recommend Valkey (a Linux Foundation fork) for cleaner licensing: same wire protocol, same drivers.
Why also offer Valkey?+
Redis's license change put the upstream project under a source-available license that restricts redistribution. Valkey is the Linux Foundation's BSD-licensed fork of the last truly-open Redis version. For greenfield projects, Valkey is the safer long-term bet; for existing apps that depend on the upstream version, Redis on Layerbase still works.
Can I connect with redis-cli and existing drivers?+
Yes. The endpoint speaks the standard Redis wire protocol on the allocated TLS port. redis-cli, ioredis, redis-py, go-redis, Jedis: anything that talks Redis works. The connection string format matches what you would point at a self-hosted Redis.
Is there a serverless / HTTP driver?+
Yes. Redis-family databases on Layerbase also speak the Upstash REST API, picked via the hostname suffix. That makes it usable from Cloudflare Workers and other edge runtimes that cannot hold a TCP connection.
What about persistence and backups?+
AOF persistence is enabled by default on every Redis database. Paid plans add scheduled snapshots (7d or 30d retention) with one-click restore. Free databases keep AOF persistence; backups become available on paid plans.