What is in the cluster
A three-node cluster the way a small platform team would set one up: Argo CD delivering the workloads, ingress-nginx and cert-manager at the edge, Prometheus and Grafana for monitoring, Jenkins for CI, and the StackRadar scanner watching all of it. Each release is pinned to the chart version helm install would have picked a few months ago, so every one of them is a little behind and the dashboard has upgrades to recommend, the way a real cluster does.
The container images those charts ship were inventoried by the pipeline the StackRadar scanner uses, and their packages are matched against live OSV advisory data. When a new CVE lands for one of those images, the demo shows it. What is simulated is the cluster itself: no pod is running anywhere, and a reporter checks in on the scanner's behalf so the cluster reads as connected.
What you can do
- Read everything a member can. The cluster overview and its Radar Score, the workloads and the images each one runs, the packages inside every image, and every finding with its severity, EPSS probability, CISA KEV flag, fixed version and affected pods.
- Change nothing. Every visitor shares one demo organisation, and the server refuses every write on it. Settings, invitations, billing, suppressions and deletions are refused or not drawn at all.
- Leave when you like. The session lasts two hours and is not tied to you. Open the demo again for a fresh one.
Then try it on your own cluster
The demo shows what the dashboard looks like once a scanner is reporting. To see your own images instead, the open-source StackRadar CLI scans the pods your kubeconfig can see from your laptop, in about a minute, with nothing installed in the cluster and no account. The quick start installs the scanner with one Helm command; the free tier covers one cluster.
Frequently asked questions
Do I need an account to use the StackRadar demo?
No. Opening the demo signs you in as a shared, read-only demo user for two hours. There is no form, no email and nothing to confirm; when the session ends, open the demo again for a new one.
Is the data in the demo real?
The findings are real; the cluster is not. The demo describes a three-node cluster running argo-cd, ingress-nginx, cert-manager, prometheus, grafana and jenkins, each pinned to the chart version helm would have installed a few months ago. The container images those charts ship were inventoried by the same pipeline the StackRadar scanner uses, and their packages are matched against live OSV advisory data, so a new CVE shows up in the demo the way it would in your own cluster. No pod is running anywhere.
Can I break something in the demo?
No. Every visitor shares one demo organisation and the server refuses every write on it: settings, invitations, billing, suppressions, deletions. You can look at everything and change nothing, so what you see is what the next visitor sees.
What can I see in the demo?
Everything a member of an organisation sees: the cluster overview with its Radar Score, the workloads and the images they run, the packages inside each image, and every finding with its severity, EPSS probability, CISA KEV flag, fixed version and the pods it affects.
Is my activity in the demo recorded?
Yes. We use PostHog, in its EU region, to count pageviews and to replay how visitors move through the demo: clicks and scrolling, with form fields masked. Recordings are attached to an anonymous session, not to a person, and nothing is stored on your device. The privacy policy has the details.
How do I try StackRadar on my own cluster?
Two ways. The open-source StackRadar CLI scans the images running in your current kubeconfig context from your laptop in about a minute, with no install in the cluster and no account. The StackRadar scanner is a Helm chart that keeps doing it continuously and reports into the same dashboard you see in the demo; the free tier covers one cluster.