Comparison
PodSteer vs Radar
An open-source Kubernetes UI that runs as a binary, in the cluster, or as a hosted service.
What Radar is
Radar is a single Go binary that serves a Kubernetes interface — topology, event timelines, Helm, GitOps, traffic, cost, a cluster audit and an upgrade-impact check — and it is the most ambitious open-source client in this list. Apache-2.0, no account needed to run it locally, and the same product also ships as a desktop app, installs into a cluster with Helm, or runs hosted as Radar Cloud. It is the tool PodSteer is most often measured against, and the comparison is a real one rather than a straw man.
Side by side
The differences that matter.
| Aspect | Radar | PodSteer |
|---|---|---|
| Licence | Apache-2.0 | Apache-2.0 |
| How it runs | A binary serving a browser UI, a desktop app, a Helm install in the cluster, or Radar Cloud | A desktop application, and only that |
| Account | None for the local binary; Radar Cloud is an account | None, in any mode |
| Platforms and packages | The CLI for macOS, Linux and Windows; the desktop app as a macOS universal .zip and Homebrew cask, a Linux amd64 .deb, .rpm and tarball, and a Windows .zip or Scoop | macOS: a signed, notarised universal .dmg and .zip, and a Homebrew cask. Linux (amd64, arm64): AppImage, .deb, .rpm and .zip. Windows (amd64): an installer and a .zip, not code-signed, so SmartScreen warns on first launch |
| Paid tiers | Radar Cloud: free to 3 clusters, then $149 and $299 per cluster per month | None — there is no paid tier of the client |
| Telemetry | Usage reporting is off unless you opt in; then anonymous usage counts and coarse cluster facts | None, and no opt-in to offer; one daily update check that turns off with one switch |
| Several clusters at once | One kubeconfig context at a time, switched in place; Radar Cloud for a fleet | Real tabs, several clusters open together, plus an All-clusters view |
| Cluster checks | A 31-check best-practice audit, and an upgrade-impact check reviewed through Kubernetes 1.37 | Findings ranked by what to do next, with the reasoning, including APIs the next Kubernetes version removes |
| Helm | Upgrade, rollback and uninstall from the UI, with chart upgrades tracked | Releases and revisions read; upgrade and rollback shown as commands to run, not run for you |
| MCP server | On by default; diagnosis read-only, with restart, scale, apply and rollback offered for the client to confirm | podsteer mcp, read-only over stdio with no port opened; there are no write tools at all |
| When metrics are missing | Missing or partial data labelled in its workload metrics | The denominator is named, and an unmeasured figure says so rather than reading as zero |
| Topology | The whole cluster or chosen namespaces; grouped by namespace or app label, or ungrouped; filtered by kind; kept live over server-sent events | One namespace, several or all; grouped by namespace, app label or any label, collapsible; kind toggles with complete counts; PodSteer's findings shown on the boxes; a Changed — Refresh badge, with Live mode opt-in |
| Traffic sources | Hubble through Hubble Relay's flow API, Istio, Caretta and Grafana Beyla | Istio, Linkerd, Beyla or OBI, Caretta, and Hubble's Prometheus metrics, read from the cluster's own Prometheus; not Hubble Relay |
| Installs anything in the cluster to see traffic | Offers a setup wizard that installs a traffic source with Helm when none is detected | Never; when no source is found it names what would be needed |
| NetworkPolicies on the map | Optional allowed, blocked or unprotected marking of edges from a static evaluation | Drawn as what each policy selects; allow and block are not evaluated |
Every claim about Radar above was checked against the Radar repository and the Radar pricing page and the v1.15.0 release assets and its traffic sources in October 2026. Projects change; if something here is out of date, tell us and we will correct it.
Be honest
When Radar is the better choice.
Choose Radar when you want ONE thing serving a whole team — an install in the cluster with an ingress, shared timelines, SSO and audit retention in Radar Cloud. Its topology and traffic still do things PodSteer's do not: it reads Cilium flows straight from Hubble Relay, marks edges allowed or blocked from a static NetworkPolicy evaluation, shows an Argo Rollout's canary and stable split, and will install a traffic source for you with Helm where PodSteer only tells you what is missing. It also runs Helm upgrades and rollbacks for you where PodSteer hands you the command, and it has a cost view where PodSteer has none. If you want the interface reachable from a browser without installing anything on a laptop, PodSteer simply does not do that.
The other way round
When PodSteer fits.
PodSteer fits when nothing should be installed in the cluster and nothing should leave the machine: it is a desktop application that reads your kubeconfig, holds several clusters open in tabs with one view across them, has no telemetry to opt in to, and makes one call beyond your clusters — a daily update check you can switch off. Its MCP server cannot write to a cluster at all, which is a simpler thing to approve than one whose writes need confirming. Its topology reads traffic from Linkerd as well as Istio, Beyla, Caretta and Hubble's metrics, puts its own findings on the map, and never installs anything to do it. There is no hosted tier to graduate to, which is either the point or a limitation depending on what you are buying.
Questions
What people ask about this comparison.
What is the difference between PodSteer and Radar?
Both are Apache-2.0, written in Go, and need no account. Radar is a binary that serves a browser UI, also packaged as a desktop app and installable in the cluster for a team, with a hosted tier. PodSteer is a desktop application only, keeps several clusters open in tabs, and has no telemetry, opt-in or otherwise.
Does PodSteer have a topology and traffic view like Radar?
Yes, from v0.6.0. Its Topology page maps one namespace, several or the whole cluster, with its findings on the boxes, and an optional traffic layer reads Istio, Linkerd, Beyla, Caretta or Hubble metrics from the cluster's own Prometheus. Radar also reads Hubble Relay directly, evaluates NetworkPolicies as allowed or blocked, and can install a traffic source with Helm; PodSteer does none of those.
Does PodSteer have a paid cloud tier like Radar Cloud?
No. There is no paid tier of the client. If paid services for teams follow later they will stand alongside the free application, not be carved out of it.