Skip to main content
Radar comes in two flavors. The cluster-side binary is identical in both. Cloud adds a hosted, multi-tenant control plane on top: orgs, RBAC, SSO, billing, audit log, fleet views. No cluster-side capability is hidden behind Cloud — everything the in-cluster binary does (topology, resources, Helm, GitOps, audit checks, MCP, per-user RBAC enforcement) ships in OSS; what Cloud adds is the control plane itself.

​
Side by side

​
Which one fits you

Pick OSS if you...

  • Want a fast, ad-hoc replacement for kubectl and the K8s dashboard, on your own machine.
  • Need to run Radar in an air-gapped environment.
  • Are comfortable wiring auth (oauth2-proxy, OIDC) yourself for a shared in-cluster install.
  • Prefer self-hosted with no vendor in the loop.

Pick Cloud if you...

  • Manage more than one cluster and want them all behind a single URL.
  • Have a team and want central role-based access, invitations, and an audit trail.
  • Want SSO without configuring OIDC per cluster.
  • Want to give Claude / Cursor / Claude Code MCP access to your clusters without managing tokens per cluster.
  • Want fleet-wide views: which clusters have audit failures, which packages are drifting, where a resource lives across clusters.

​
Use both at once

Run OSS locally against your dev cluster while your team uses Cloud for shared environments. Same binary; the only difference is whether cloud.enabled is set in Helm.

​
Switch later

  • OSS → Cloud: install the chart with cloud.enabled=true against the same cluster.
  • Cloud → OSS: drop the cloud.* Helm values and Radar reverts to a self-contained in-cluster install.
K8s is the source of truth in both cases - there’s no Radar-side data format to migrate.