Redis

Redis is an in-memory store, extremely fast for caching, sessions, rate limits, queues, and simple real-time data. In dFlow it’s a Database service like Postgres or MySQL, with its own connection string on Overview.

How databases work in dFlow: Databases overview

On this page

• When Redis is a good fit
• Create and deploy
• Connection URL and fields (including username display)
• Reference variables (REDIS_…)
• Expose
• Managing the service

When to choose Redis

Choose Redis when you need low latency and can fit working data in memory (persistence options depend on how your instance is provisioned). It’s not a replacement for a full SQL or document database for your primary business data; pair it with Postgres, MySQL, or MongoDB when you need both.

Set up Redis in dFlow

1. Applications → Environment → Add New → Add service → Database → Redis.
2. Create Service → Deploy.
3. Wait until Deploy completes; dFlow handles server setup for you.

Your connection details

After deploy, Overview shows:

• Connection URL: usually redis://… with authentication in the URL.
• Username: dFlow may show default next to the URL for clarity (common Redis pattern).
• Password, hostname, port.

There isn’t always a separate “database name” row for Redis the way there is for SQL. The URL or HOST / PORT / PASSWORD fields are what most clients need.

Public credentials appear after Expose. Unexpose before Stop if exposed.

Link your app with reference variables

On your app or Docker service, open the Variables tab and use { } Reference variables:

{{ my-redis.REDIS_URI }}

Internet access (Expose)

Redis uses one public port when exposed, same pattern as Postgres and MySQL. Prefer internal URLs for services running on dFlow.

Day-to-day management

Restart, Stop, and Expose / Unexpose follow the same rules as other databases. See Where things live in the dashboard.

Useful links

• Redis
• Redis source