Platform · Redis

Redis you can trust with your hot path.

Managed Redis with dedicated per-tenant processes — not a shared multi-tenant cluster. Sub-millisecond reads, AOF + RDB persistence, and isolation that holds under load.

Isolation by default, not by configuration

On Luceris, every Redis tenant gets its own `redis-server` process listening on a dedicated port behind the proxy. There is no shared memory, no shared keyspace, no noisy-neighbor risk. The proxy validates credentials against a 60-second bcrypt-cached DDB lookup, then forwards bytes — no command rewriting, no surprise behavior.

Per-tenant processes

One `redis-server` per tenant on 127.0.0.1:7000–7999. No shared keyspace, no eviction storms from someone else's workload.

Persistence options

AOF (default, durable), RDB (snapshot), or none (pure cache). Choose per cluster; switch at any time without downtime.

Data structures

Strings, lists, hashes, sets, sorted sets, streams, hyperloglog, bitmaps, geospatial. Lua scripting and Redis Functions supported.

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 policies

noeviction, allkeys-lru, allkeys-lfu, volatile-lru, volatile-lfu, allkeys-random, volatile-random, volatile-ttl. Set per cluster.

TLS-only ingress

No plaintext connections. TLS 1.3 with modern ciphers. Optional IP allowlists on the Contact-us tier.
Cluster specs
Max memory (Free)256 MB
Max memory (Contact-us)On request — tiers up to 1 TB
PersistenceAOF, RDB, or none (configurable)
Persistence guaranteefsync every second (default); every write on request
Eviction8 policies (LRU / LFU / random / TTL variants)
Wire compatibilityRedis 7.x
Hosting regionEU (France primary, Germany replica)

Quickstart

bash
Connect with redis-cli
# Get the connection string from the Luceris dashboard
export REDIS_URL='rediss://default:••••••••@cli.luceris.cloud:6380'

redis-cli -u "$REDIS_URL" SET hello world
redis-cli -u "$REDIS_URL" GET hello
# "world"

Ideal 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

Is this Redis OSS or Redis Enterprise?
Redis OSS 7.x. We run upstream binaries; we do not maintain a fork or strip features.
Can I run a multi-shard cluster?
Sharded Redis is available on the Contact-us tier. The Free tier is single-shard per cluster — fine for caches up to ~256 MB.
What happens when memory fills up?
It depends on the eviction policy you set. `noeviction` rejects writes; `allkeys-lru` evicts the least-recently-used key; `volatile-ttl` evicts the soonest-expiring volatile key. Default is `allkeys-lru` for cache-style clusters.

Sub-millisecond reads, on your terms.

Free tier includes a 256 MB Redis with AOF persistence and TLS-only ingress.