We built Radar in the open. Radar is how we make it work for teams.
A Kubernetes visibility tool built by the platform team at Skyhook, released as Apache 2.0, and now packaged as a hosted SaaS — without abandoning the community that got us here.
Radar started as a Slack channel called #why-cant-we-see-this.
Skyhook is a Kubernetes platform. Building one means running clusters — lots of them, on every cloud, for every customer. And running clusters means debugging them. At 2am. On call. Alone.
We tried every Kubernetes visibility tool the market had. Desktop apps that needed kubeconfigs. CLIs that showed one cluster at a time. Commercial SaaS that gated SSO behind the Enterprise tier and wanted a demo before telling us the price. None of them were built for what we were actually doing: running a fleet, on-call, as a team, forever.
So we built a tool. Internal at first. Then we realized every platform team we'd ever worked on had the same problem. So we open-sourced it under Apache 2.0 and pushed it to github.com/skyhook-io/radar.
The response told us we weren't alone. 1.2k GitHub stars in months. Pull requests from engineers we'd never met. Slack messages saying “this replaced three tools for us.” But also: “I love it on my laptop, but how do I share this with my team?” “Can I see all my clusters at once?” “I need the events to persist for our audit.”
Radar is the answer to those questions. A hosted control plane that sits on top of the OSS — with the multi-cluster view, the long retention, the SSO, and the collaboration layer teams actually need.
Why Radar has its own brand but shares a team.
People ask this all the time. Here's the honest explanation.
Skyhook is the parent company and the flagship product — a Kubernetes deployment platform that makes shipping to production as simple as a PaaS, without the lock-in.
Radar was born out of Skyhook's own platform engineering work. We couldn't build a great deployment experience without a great visibility layer underneath it — so we built both.
Visit skyhook.ioRadar is its own product, its own brand, and its own buying decision. Platform teams can adopt it without taking a position on the whole Skyhook platform.
It shares a team, a company, an investor base, and a Slack with Skyhook. It doesn't share a codebase, a deployment, or a sign-up funnel. The two products sit next to each other — they don't depend on each other.
Explore the productShort version: Skyhook is the company. Radar OSS is the open-source project. Radar Cloud is the hosted commercial version of that project. All three exist because the same team couldn't stop caring about Kubernetes.
Built by engineers who've been on the other end of the pager.
Same team behind Skyhook. Same obsession with making Kubernetes feel less like a hostile operating environment.
Nadav Erell
CEO
Former Staff Engineer at Google where he led teams building cloud infrastructure, identity, and data platforms at planetary scale. Co-founded Skyhook to bring Google-grade platform engineering to every company — which led us straight to the Kubernetes visibility problem that became Radar.
LinkedIn
Eyal Dulberg
CTO
Former Chief Architect at OneZero and eToro with deep experience running high-availability Kubernetes platforms serving millions of fintech users. Designed Radar's engine to be what he wished he'd had at 2am during a dozen production incidents. Now writing the open-source code he'd want to inherit.
LinkedIn
Roy Libman
CPO
Former Product Lead at Armis and Head of Product Growth at eToro. Seven years building platforms at scale with a software-engineer's instinct for developer tools. Runs product for Radar — which means making sure the OSS stays dev-first and the SaaS stays team-first.
LinkedInFour principles that shape what we ship — and what we don't.
Open-core by conviction
Radar stays Apache 2.0. Not a tease, not a throttled preview. The same engine you'd fork on GitHub is the engine Radar runs in your cluster. We've written down four specific commitments to the community on our Open Source page — and made them the kind of promises that are hard to walk back quietly.
Transparency over lock-in
Published pricing, no custom quotes until Enterprise. Honest competitor comparisons (including where they win). Public roadmap. Source code you can read. If we've hidden something important, call us out — radar@skyhook.io — and we'll fix the page.
Visibility is a team sport
The moment a tool saves five minutes of kubectl roulette, twenty people want to use it. We refuse to punish that with per-seat pricing. Radar charges per cluster so the whole team gets in — dev, SRE, manager, intern. The value scales with the infrastructure, not the headcount.
Ship in public
We cut a Radar release every week and write up what changed on the Changelog page. We host monthly office hours. Issues on GitHub get a first-pass response within 48 hours. The whole point of open source is that you can tell whether we're actually working — so we try to make that easy to check.
Y Combinator and the engineers who've been there.
We're building for the long arc. Our backers are the kind who understand why that matters for an open-source company — and why we're writing our OSS commitments down rather than keeping them as vibes.
There are several ways in.
We're hiring
Platform engineers, infra SWEs, and a designer who has opinions. Radar roles are listed alongside Skyhook's.
View open rolesHang out in the community
Slack, GitHub Discussions, monthly office hours. The fastest way to talk to a maintainer.
Community hubJust say hi
Questions, feedback, war stories, product requests — radar@skyhook.io reaches one of the three of us directly.
radar@skyhook.ioSpin up Radar on a cluster. See if we built what you needed.
Apache 2.0 OSS or hosted free for 3 clusters. Install in 60 seconds. If it's not for you, uninstall is a single kubectl command.
Apache 2.0 OSS · Unlimited clusters self-hosted · Hosted free tier for up to 3 clusters