Support

Create an account, choose the projects you care about, and set your notification frequency. Your dashboard will show the latest releases instantly.

I built KubeBuddy Radar because I was struggling to keep up with the releases running across customer clusters. Now it keeps everything in one place and sends easy-to-read updates that call out breaking changes and security fixes, so I can act fast without living in release notes.

Yes. Security fixes are highlighted so you can prioritize critical upgrades faster.

Visit your dashboard, open a project, and adjust the email frequency or release types.

Choose immediate alerts, daily digests, or weekly summaries per project. You can also enable webhooks on Pro.

We cover CNCF projects and essential DevOps tools across orchestration, CI/CD, service mesh, observability, security, and networking.

Open the Account page to upgrade, change payment methods, or manage your subscription.

Platform engineers, SREs, and DevOps teams who maintain multiple clusters and tools. If you are responsible for upgrades, Radar is built for you.

We track over 150 projects including all CNCF graduated, incubating, and sandbox releases such as Kubernetes, Prometheus, Helm, ArgoCD, Cilium, and Istio plus essential DevOps tooling across observability, networking, and security. Check the projects page to see everything currently tracked.

Create an account, choose the projects you care about, and set your notification frequency. Your dashboard will show the latest releases instantly.

Open the Account page to upgrade, change payment methods, or manage your subscription.

We cover CNCF projects and essential DevOps tools across orchestration, CI/CD, service mesh, observability, security, and networking.

Choose immediate alerts, daily digests, or weekly summaries per project. You can also enable webhooks on Pro.

Visit your dashboard, open a project, and adjust the email frequency or release types.

Yes, Pro users can add custom labels to group projects by environment, cluster, or team. Labels are encrypted at rest and included in notifications and API responses, which makes filtering and organizing subscriptions much easier.

Yes. Webhook URLs and API keys are encrypted at rest in the database using AES-256. We only decrypt them when actually sending notifications or handling API requests, and we use prepared statements everywhere to prevent SQL injection.

Yes. Security fixes are highlighted so you can prioritize critical upgrades faster.

Pick your cadence per project: every release, daily digest, or weekly summary. By default you only get notified about stable releases (no pre-releases cluttering your inbox). Enable betas per subscription if you want to track them.

Free users can subscribe to 10 projects with email notifications and basic settings. It's a great way to cover your top tools before deciding if you want unlimited tracking.

Unlimited project subscriptions, webhook integrations (Slack, Teams, custom endpoints), API keys for programmatic access, and custom labels. This lets you integrate Radar into your existing workflows instead of relying solely on email.

No. The catalog and user endpoints require either a logged-in browser session or an API key. This keeps the data private to your account and prevents anonymous scraping.

Yes - but it's focused on readability. AI helps summarize long changelogs and highlight breaking changes and security fixes while still showing the source links so you can verify everything.

Releases with security fixes are flagged automatically, and we pull in CVE details when available. This helps you identify what needs patching without digging through changelogs.

Absolutely. Use the request form and tell us why it matters to your team. Requests are reviewed weekly and CNCF projects in production get priority.

Next up: edge cache rollout for faster dashboards, CLI support, GitHub integrations, and wider Git provider coverage. Each launch is announced as soon as it is ready.

Releases are checked frequently throughout the day with a daily sweep to catch anything that slipped through. The full catalog syncs once per week to pick up new repos and metadata changes.

Impact labels help you quickly understand what type of changes are in a release. Labels include: Breaking change (requires migration work), Config/default change (settings or defaults shifted), Deprecation (feature removal warnings), Dependency bump (underlying libraries upgraded), and Feature (new capabilities added). These labels appear as colored badges on release cards alongside security and version type indicators.