Connect Redis to Warp
Give Warp governed access to Redis through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Redis to Warp in four steps
Admins approve the server once. Everyone in Warp then gets it through the same governed connection.
- 1
Approve Redis in Runlayer
Add Redis from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Warp to Runlayer
Users add the Runlayer Plugin to Warp by following Runlayer’s setup guide. Warp reaches Redis’s tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Warp setup guide - 3
Sign in to Redis
An admin adds Redis credentials to Runlayer once. They never sit in the client’s configuration.
- 4
Use Redis from Warp
Redis’s approved tools appear in Warp. Every call is checked against policy and recorded.
Tools
Redis tools in Warp
Redis reports its tools when your organization connects it, so the list depends on your deployment.
Control
What Runlayer can see and stop in Warp
Some controls apply to every client at the gateway. Others depend on what Warp exposes to Runlayer.
Gateway policy (available)
Every Redis call from Warp passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Warp as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Warp yet, so control happens at the gateway.
Frequently asked questions
Connect more