Quickstart with Radar Cloud

Sign up, install the Helm chart, share fleet views with your team. Free tier: 3 clusters, unlimited members. For the architecture, see Cloud overview.

Go to app.radarhq.io and authenticate with Google, a passkey, or an email magic link. New users are routed through the sign-up flow on the same page.

Name your organization

First-time users land on an onboarding page. If your email domain isn’t a free-mail provider (gmail.com, outlook.com, etc.), we’ll suggest a name based on it. You can change it later under Settings → Organization.

Connect a cluster

From the home page, click Connect a cluster (or go to /install). Give the cluster a name and click Generate install command.You’ll see an install command with your cluster ID and cluster token baked in (the token is shown only once). It stores the token in a Kubernetes Secret, then installs Radar with Helm:

helm repo add skyhook https://skyhook-io.github.io/helm-charts
helm repo update skyhook
kubectl create namespace radar --dry-run=client -o yaml | kubectl apply -f -
kubectl create secret generic radar-cloud-config -n radar \
  --from-literal=token=rhc_... \
  --dry-run=client -o yaml | kubectl apply -f -
helm upgrade --install radar skyhook/radar -n radar \
  --set cloud.enabled=true \
  --set cloud.url=wss://api.radarhq.io/agent \
  --set cloud.insecureSkipVerify=false \
  --set cloud.clusterName=<cluster_id> \
  --set cloud.existingSecret=radar-cloud-config \
  --set auth.mode=proxy \
  --set rbac.helm=true \
  --set rbac.secrets=true \
  --set rbac.podExec=true \
  --set rbac.portForward=true \
  --set rbac.metrics=true \
  --set rbac.selfUpgrade=true

Run that against the cluster you want to connect. The page polls for up to 5 minutes; once the in-cluster Radar reaches the control plane, you’ll be redirected into the cluster view.

The token is shown once. If you lose it, rotate it from Clusters → cluster → Rotate token. The old token keeps working until Radar connects with the new one (or for 24 hours), so a connected cluster stays online while you apply it.

Use Radar

Once connected, you’ll see the same Radar UI as the OSS binary - topology, resources, timeline, audit, Helm, GitOps, traffic, cost, MCP. Cloud adds:

Cluster switcher in the top nav for jumping between connected clusters.
Fleet views at /fleet/* - cross-cluster problems, search, checks, and package drift.
Disconnected banner if the in-cluster Radar stops reaching the control plane.

Invite your team

Open Settings → Organization → Members, enter email addresses under Invite your team, and pick a role:

Owner - full admin, including billing and destructive ops.
Member - operational access (view + standard mutations).
Viewer - read-only.

If everyone on your team uses the same email domain, set up domain auto-join so new sign-ups land in the org automatically.

Wire AI tools (optional)

Radar Cloud exposes per-cluster MCP endpoints so Claude Code, Codex, Cursor, GitHub Copilot, OpenCode, Google Antigravity, and any other MCP client can read and operate on your clusters. Open Agents, pick your client, and follow its setup instructions. See Personal access tokens and AI via MCP.

What’s next

Connecting a cluster

Install options, RBAC flags, troubleshooting.

Organizations & roles

The permission model in detail.

SSO

SAML / OIDC self-serve setup.

Billing & plans

Free tier, Team, Enterprise, Custom.

Get started

Views

In-cluster capabilities

Integrations

Local & in-cluster setup

Cloud

Reference

Quickstart with Radar Cloud

What’s next

Connecting a cluster

Organizations & roles

SSO

Billing & plans

​What’s next

Connecting a cluster

Organizations & roles

SSO

Billing & plans

What’s next