# Introducing Redis Radar: a single view for your whole Redis fleet

**Tagline:** News & Media | **Authors:** Kurt Moeller | **Categories:** Tech | **Published:** 2026-09-22 | **Updated:** 2026-09-22

Redis environments grow across teams, applications, and infrastructure. You might run Redis Software on-premises, use Redis Cloud for another application, and have Redis Open Source or a cloud provider's managed Redis somewhere else. Even a fleet built entirely on Redis Software can grow to dozens of clusters, each with its own admin console. Keeping track of all of it means hopping between consoles and recording what you find by hand.

Today we're introducing Redis Radar, now generally available. Radar brings inventory, health, and usage data from every Redis deployment you run, across Redis Software, Redis Cloud, Redis Open Source, Amazon ElastiCache, and Google Memorystore, into one place. It shows you what you're running, where it's running, and what needs attention, so you can stop assembling the picture and start acting on it.

## Connect your deployments

Redis Radar is available as a fully managed service and as self-managed software. In the managed service, you sign in at [radar.redis.io](http://radar.redis.io) with your Redis Cloud credentials and connect the Redis deployments you want to see.

For secure or air-gapped environments, you can run self-managed Radar entirely inside your own infrastructure, installed via Helm chart, RPM, or Docker Compose.

Connecting is simple. To view your Redis Cloud data, link one or more Redis Cloud accounts with an API key and bring their deployments into a shared view.

For self-managed Redis (both Redis Software and Redis Open Source), you point Radar at each cluster with read-only credentials. For clusters Radar can't reach directly, such as those behind a firewall or on a private network, install the lightweight Radar agent inside your environment. It connects out to Radar over TLS, so Radar never needs inbound access. Either way, Radar collects only the metrics and metadata needed to describe your deployments, never the application data stored in them.

Radar can also ingest metrics from your Amazon ElastiCache and Google Memorystore databases. For ElastiCache, you provide read-only AWS credentials and the regions to scan; for Memorystore, a read-only service account plus the project and regions. Memorystore connections cover the Redis, Valkey, and Memcached engines.

![Redis Radar](https://cdn.sanity.io/images/sy1jschh/production/d92db85dd8056d56decc5c225af2641e40fcf8c5-1675x1016.png)

## Radar’s fleet level view

Radar collects and displays a variety of information, and information available depends on the Redis deployment type.

| View | What it helps you understand |
| --- | --- |
| Inventory | Which deployments and databases you have, and where they’re running |
| Versions | Which versions are in use across your connected deployments |
| Health | The latest reported state of deployments and databases |
| Usage | Memory usage and capacity information to help assess utilization |
| Alerts | Active Redis Software alerts and status findings from Redis Cloud and Redis Open Source |
| Security settings | Configuration details such as whether TLS is enabled, where available |
| Licenses | License usage and expiration across Redis Software clusters |
| Certificates | Certificate status and upcoming expirations for Redis Software |

## Why a fleet view matters

Aggregating information from your entire Redis fleet into a single tool allows you to efficiently view the state of all your Redis deployments and drill further into cluster or database health.

**Easily find what needs attention**

A certificate approaching expiration is easy to overlook when you have to check clusters individually. Seeing it alongside the rest of your Redis Software fleet makes it easier to plan the renewal.

The same applies to a database reporting an unhealthy state or a node under memory pressure. Radar brings those signals into context, so you can identify the affected resource and investigate. You spend less effort assembling the picture before deciding what to do.

**Make routine planning easier**

A database version review starts with knowing what’s deployed. A capacity discussion begins with knowing where memory is being used across a variety of databases. A license renewal starts with understanding usage and expiration across your clusters. Radar consolidates all that information within reach.

For anyone responsible for keeping Redis running, that means a more consistent starting point for both daily checks and longer-term planning.

## Get started

You can get started with Radar by logging into the fully-managed service at [radar.redis.io](http://radar.redis.io) or by getting the self-managed software version [here](https://redis.io/docs/latest/operate/radar/install/). Next, link your Redis Cloud accounts or install and connect your Redis Software or Open Source clusters directly or through the Radar agent. Then, review the overview, open a database, and check what needs attention. That’s the goal of Radar: make your Redis estate easier to understand, so you can spend more time acting on what you find.