Engineering
How Radar works under the hood - Kubernetes internals, informers, topology, and the engineering behind the product.
Read-Only Is Not a Safety Boundary
Two sentences get said in every meeting where a team wires an AI agent into a cluster: it's read-only, and just use the service account. Both are wrong later.
Radar MCP vs kubectl: A Kubernetes Agent Benchmark on 52 Faults
We benchmarked Radar's Kubernetes MCP server against raw kubectl on 52 live-cluster faults. Radar improved diagnosis quality and cut tool calls by 76%.
MCP for Kubernetes: Live Cluster Context for AI Tools
Pointing an AI at raw kubectl works, badly. Radar's built-in MCP server gives Claude, Cursor, and friends a token-optimized, RBAC-aware view of your cluster.
Why Radar Cloud Doesn't Cache Your Cluster State
Most multi-cluster dashboards copy your cluster state into a backend cache. Radar Cloud doesn't. Here's why the reverse-proxy model is the right call.
Radar's In-Cluster Architecture: Outbound-Only, Scoped, Live by Default
How Radar's in-cluster install works: outbound-only TLS, read-only RBAC by default, ~32MB RSS. The five questions every platform team asks, answered.
Five Questions You Can't Answer With kubectl
kubectl hands you one object at a time, as raw YAML. Here are five questions - relationships, isolation, image contents, history, posture - where that runs out of road.
Cluster Audit: The 31 Checks That Catch What You Forgot
Most clusters fail the same checks. Radar's built-in audit runs 31 of them inline against your live state. Inspired by Polaris and the NSA / CISA hardening guide.
Bring your first cluster online in 60 seconds.
Install the Helm chart, paste a token, see your cluster. No credit card required.
Apache 2.0 OSS · Unlimited clusters self-hosted · Hosted free tier for up to 3 clusters