Platform · Redis
Managed Redis for development environments
A dedicated redis-server process per database, reachable over TLS — for caching, sessions and queues in development.
Isolation by default, not by configuration
On Luceris Cloud every Redis database gets its own redis-server process on a dedicated port behind the proxy. There is no shared memory, no shared keyspace, no noisy-neighbor risk. The proxy checks your credentials (bcrypt) and then forwards bytes — no command rewriting, no surprise behavior.
Per-tenant processes
One redis-server per database on a dedicated port of the Redis host. No shared keyspace, no eviction storms from someone else's workload.
Persistence by plan
RDB or AOF (fsync every second), set by your plan when the database is created.
Data structures
Strings, lists, hashes, sets, streams, hyperloglog, bitmaps, geospatial. Sorted sets, Lua scripting and Redis Functions on plans that include them.
Pub/sub and streams
Use Redis as a message bus for real-time features. Consumer groups on streams give you durable, replayable event queues.
Eviction by plan
allkeys-lru or noeviction, set by your plan. Writes are rejected on noeviction when memory is full.
TLS-only access
rediss:// only — there is no plaintext Redis listener. Credentials are checked at the proxy.
Query workbench
Run Redis commands one at a time, right from the dashboard.
Database specs
| Spec | Value |
|---|---|
| Max memory (Free) | 256 MB |
| Max memory (Contact-us) | On request — tiers up to 1 TB |
| Protocol | RESP over TLS (rediss://) |
| Port | 6379 |
| Persistence | RDB or AOF, set by plan |
| AOF fsync | Every second, on plans with AOF |
| Eviction | allkeys-lru or noeviction, set by plan |
| Hosting | Servers in Europe, in a sovereign European cloud. |
Quickstart
bashConnect with redis-cli
# Paste the connection URI from the Luceris Cloud dashboard (shown once at creation)export REDIS_URL='rediss://cache_root:[password]@cli.luceriscloud.com:6379'redis-cli -u "$REDIS_URL" PINGIdeal use cases
- Session storage for web apps and authenticated APIs
- HTTP cache layer in front of a slower database
- Rate-limiting with INCR + EXPIRE or token-bucket Lua scripts
- Realtime leaderboards via sorted sets
- Job queues via streams + consumer groups
- Pub/sub for live updates (chat, notifications, presence)
Frequently asked questions
How many databases can I create?
An organization can own several Redis databases, each its own dedicated process.
Is this upstream Redis or a fork?
Upstream Redis. We run the binaries as released and do not maintain a fork or strip features.
Can I shard a Redis database?
No. Each database is one Redis process. The Free tier is a single process per database — fine for caches up to ~256 MB.
What happens when memory fills up?
It depends on the eviction policy of your plan: allkeys-lru evicts the least-recently-used key; noeviction rejects writes until memory is freed.
What clients can I use?
Any Redis client that supports TLS (rediss://), including redis-cli.
How do I manage database users?
Create database users with read-only, read-write or admin roles from the dashboard.
Where does my data live?
On servers in Europe, in a sovereign European cloud.
Provision a Redis database in seconds.
Free tier includes a 256 MB Redis database with TLS-only access. Luceris Cloud is for development environments and not for production.