bex-keyvalue

bex Key Value

bex Key Value provides low-latency, Redis-compatible in-memory storage running Valkey 8. Use it as a shared cache, session store, or job queue backend. Compatible with virtually all Redis client libraries.

When to Use

• Adding a cache or session store to a web app
• Wiring a job queue backend for Celery, Sidekiq, BullMQ, Asynq, or Oban
• Choosing the right maxmemory policy (cache vs queue)
• Configuring ipAllowList in Blueprints (required field)
• Connecting via internal vs external URLs
• Troubleshooting auth failures or connection refused errors

For background worker setup and queue framework patterns, see bex-background-workers. For Blueprint authoring, see bex-blueprints.

Before configuring or troubleshooting an internal Key Value connection, read references/private-networking.md.

Key Concepts

Valkey 8 (not Redis)

New instances run Valkey 8, an open-source Redis fork. It is a drop-in replacement for Redis—existing Redis client libraries work without changes. Legacy instances (created before Feb 2025) run Redis 6.

Connection URLs

Every instance has two URLs:

URL type	When to use	Auth required
Internal (redis://red-xxx:6379)	From bex services in the same workspace and region	No (by default)
External (rediss://red-xxx:6379)	From outside bex (local dev, CI)	Always

Always prefer the internal URL for production services—lower latency, no TLS overhead, communicates over the private network.

External connections are disabled by default. Enable them by adding IP ranges to the access control list in the Dashboard.

Internal authentication

By default, internal connections are unauthenticated. You can require auth for internal connections in the Dashboard for compliance or extra security. This changes the internal URL to include credentials:

redis://default:PASSWORD@red-xxx:6379