Dragonfly Cloud

Managed Dragonfly — data store row drawer, Redis-compatible Connection URI, TLS passkey, private network prod.

Dragonfly Cloud runs the same multi-threaded engine as the Dragonfly image, with a managed endpoint. drivers.store.kv stays redis.

The one rule

Click the data store row to open the side drawer — copy the Redis-compatible Connection URI (includes passkey). Paste it as REDIS_URL.

Find credentials (current console)

Open Dragonfly Cloud → Data Stores.
Wait until Status is Active.
Click the data store row (opens the configuration drawer).
Copy:
- Redis-compatible Connection URI (e.g. rediss://default:PASS@….dragonflydb.cloud:6385)
- or host / port / default user / passkey separately
Paste the URI into REDIS_URL unchanged when it already uses rediss://.

process env

REDIS_URL=rediss://default:PASSKEY@xxxxx.dragonflydb.cloud:6385

Smoke-check: redis-cli -u "$REDIS_URL" PING.

Topic	Guidance
Public network	TLS + passkey on by default — leave TLS enabled
Private network	Recommended for production (peering) — passkey still required on public
HA	Enable high availability in the data store settings before you need failover
Driver	Same `redis` driver as self-hosted Dragonfly
Port	Drawer URI often uses 6385 (not 6379) — copy the URI wholesale

Self-hosting comparison: the Dragonfly image needs OKE_STORE_KV_PASSWORD + memlock; Cloud replaces that with the drawer passkey.

Do not reuse a self-hosted REDIS_URL without rediss:// when the drawer shows TLS.