Planekeeper is currently in alpha development. Request early access to get started.

Automated Version Drift Detection

Stop deploying software you forget to update

Planekeeper monitors your deployed software against upstream releases and alerts you when versions fall behind. It catches version drift before it turns into a security incident or a month-long migration project.

Version drift is invisible until it hurts

Your team manages dozens of applications. Helm charts pinned six months ago. Container images locked to tags that stopped receiving patches. Configuration files no one has checked since initial setup. Without active monitoring, these versions silently fall behind.

Security patches go unnoticed

Critical CVE fixes ship upstream but your pinned versions never pick them up. You only find out during an audit.

Breaking changes stack up

When you finally upgrade, the gap is so large that the migration becomes a project in itself. What should take hours takes weeks.

No one owns the problem

Without a system watching versions, nobody knows what's current and what's stale. Drift happens silently across every team.

Security-first by design

Planekeeper was built so your credentials, source code, and repository data never leave your network.

Credentials stay on the agent

SSH keys, personal access tokens, and registry credentials are configured locally on the agent. They are never sent to or stored on the Planekeeper server.

Repos cloned locally, not centrally

Agents clone repositories at your site and extract only a version string. Your source code never transits to the Planekeeper server -- only the parsed version is reported back.

Outbound-only connections

Agents only make outbound calls to poll for tasks and push results. No inbound firewall rules are needed at your site -- deploy behind NAT, VPNs, or air-gapped networks.

A five-stage pipeline that runs itself

Define your jobs and rules once. Planekeeper handles everything from there -- gathering releases, scraping your repos, evaluating rules, generating alerts, and notifying your team. Each stage triggers the next automatically.

1

Gather

Poll GitHub, Helm repos, and OCI registries for the latest upstream releases on a schedule.

2

Scrape

Clone your Git repos and parse deployed versions from YAML, JSON, or any text file.

3

Evaluate

Compare versions against your rules -- days behind, major versions behind, or minor versions behind.

4

Alert

Create severity-graded alerts that escalate automatically and resolve when you upgrade.

5

Notify

Deliver webhooks to Slack, Discord, Teams, or PagerDuty with one-click acknowledgment.

Built for infrastructure teams

Everything you need to enforce version currency across your stack.

Three source types, one pipeline

Gather releases from GitHub Releases, Helm repository indexes, and OCI container registries. Helm Sync jobs automatically discover every chart in a repository and create gather jobs for each one.

Parse any config file

Extract deployed versions from Chart.yaml, package.json, Dockerfiles, or any text file using YQ, JQ, or regex expressions. Support for private repos via SSH keys and HTTPS tokens.

Configurable rules and severity

Measure staleness by days behind, major versions behind, or minor versions behind. Each rule defines moderate, high, and critical thresholds so alerts escalate as drift grows. Exclude prereleases with stable-only mode.

Smart alerts that manage themselves

One alert per config, updated in place as conditions change. Alerts escalate when drift worsens, reset acknowledgments when versions change, and resolve automatically when you upgrade.

Notify where your team works

Route alerts to Slack, Discord, Microsoft Teams, PagerDuty, or any webhook. Use Go templates to customize payloads per platform. Notifications include one-click acknowledge URLs with HMAC-signed payloads.

Deploy agents anywhere

Lightweight agents make only outbound connections -- no inbound firewall rules needed. Deploy alongside your server or at remote sites to scrape private repos behind firewalls.

Multi-tenant by design

Every resource belongs to an organization. A shared Global organization provides common release data for popular projects so you don't duplicate work. Scope filters let you view your data, shared data, or both.

Event-driven, not just scheduled

When a gather or scrape job completes, rules re-evaluate within seconds. Create or toggle an alert config and see results immediately. No waiting for the next cron cycle.

Built for the teams who keep software running

DevOps Teams

Track Helm chart and container image versions across clusters.

Platform Engineers

Monitor infrastructure dependencies and enforce version policies.

SREs

Enforce version currency SLOs across services with graded severity alerts.

Security Teams

Ensure timely adoption of patched releases before CVEs become incidents.

Monitor what you actually deploy

Planekeeper reads version information from your actual deployment repositories -- not from a lockfile or package manager. It monitors what is deployed, not what CI last built.

GitHub Releases

Track releases from any public or private GitHub repository. Tag filtering and version regex extraction included.

kubernetes/kubernetes

Helm Repositories

Fetch chart versions from any Helm repo index. Helm Sync auto-discovers all charts in a repository.

argoproj.github.io/argo-helm/argo-cd

OCI Container Registries

Read image tags from Docker Hub, GitHub Container Registry, Quay.io, and any OCI-compliant registry.

ghcr.io/owner/image

Start catching version drift today

Set up your first monitor in under 10 minutes. No credit card required.