# Redis Radar release notes 2026.9.5

```json metadata
{
  "schema_version": 2,
  "title": "Redis Radar release notes 2026.9.5",
  "description": "Connect clusters that Radar can't reach directly by installing an agent.",
  "categories": ["docs","operate","radar"],
  "tableOfContents": {"sections":[{"children":[{"id":"connect-clusters-with-an-agent","title":"Connect clusters with an agent"}],"id":"highlights","title":"Highlights"}]}

,
  "codeExamples": []
}
```


Radar can now collect from clusters it can't reach directly. You install an agent on a host inside the network that holds them, and the agent opens an outbound connection to Radar.

This is a Short-Term Support (STS) release. See [Self-managed releases](https://redis.io/docs/latest/operate/radar/release-notes#self-managed-releases) for more details.

## Highlights

### Connect clusters with an agent

- Collect from **Redis Software** and **Redis Open Source** clusters behind a firewall, in a private subnet, or on a segmented network. Radar needs no inbound access to your network.
- Choose between two modes. **Managed** agents receive source credentials from Radar, so you add and change sources from the Radar UI. **Static** agents read their sources from a file on the agent host, so those credentials never leave it.
- Collect from a fully isolated network by exporting to a file on one host and submitting it from another.
- Install from standalone agent packages for Linux on amd64 and arm64, including Federal Information Processing Standards (FIPS) 140-3 builds.
- Track every agent under **Settings > Agents** and in the **Connected agents** list on the Connections page, with its mode, platform, version, and last heartbeat.

Radar accepts agent connections on its agent gRPC endpoint, which isn't enabled on every Radar deployment. See [Connect clusters with an agent](https://redis.io/docs/latest/operate/radar/agent).