The Draftt Language

Understand the key terms used across Draftt platform to navigate upgrades, dependencies, and infrastructure with clarity.

Policy Rules

Rules in Draftt that govern how version drift and software lifecycle status are evaluated across your infrastructure. Policies in Draftt define how version drift and software lifecycle status are assessed across your infrastructure. They determine what counts as compliant, outdated, or in need of attention.

Draftt supports two policy types: End-of-Life, Latest

End-of-Life

Compares your resource versions to official provider end-of-life(EOL) timelines to flag outdated software and calculate compliance percentages.

Latest

Tracks the most recent available version and flags resources that are behind - even if still supported. Ideal for teams that follow a “latest-version” strategy to stay consistently up-to-date.

---

Status Types

Outdated

A resource marked as Outdated is running a version that is no longer compliant with the applied policy and requires upgrade attention. In the Inventory, this means the component has fallen behind the defined policy. In the Kubernetes Catalog, it indicates version misalignments that are no longer compatible with the current Kubernetes cluster version.

Impending

A resource marked as Impending is soon to become non-compliant based on the applied policy and should be prioritized for review. In the Inventory, this flags components approaching end-of-life (within the next 6 months) or drifting from the "Latest" version policy, depending on the rule applied. In the Kubernetes Catalog, it highlights workloads that will become incompatible starting with the next Kubernetes version upgrade.

Supported

A resource marked as Supported is currently compliant with the applied policy and considered safe to run. In the Inventory, this reflects alignment with the selected policy. In the Kubernetes Catalog, it means the version is compatible with the active cluster and is not subject to upgrade or compatibility concerns.

---

Version Targets

Required Version

The Required Version is the minimum version you need to upgrade to in order to reach a provider-supported state. It reflects the lowest officially supported version according to the vendor's lifecycle documentation, allowing you to restore compliance with the least possible effort.

Recommended Version

The Recommended Version is Draftt’s suggested target based on a blend of ecosystem insights, known security vulnerabilities, support timelines, and upgrade cadence. It balances stability and time-sensitivity, helping you avoid unnecessary frequent upgrades while maintaining long-term confidence in your infrastructure.

---

Platform

Inventory

Draftt’s Inventory is your real-time map of the entire tech stack. It tracks every component connected, surfacing version details, end-of-life timelines, and risk statuses. With rich filters, forward-looking upgrade timelines, and clear impact explainability, it gives your team everything needed to plan upgrades proactively and confidently.

Catalog

The Catalog is a list of infrastructure resources detected across your environment—such as runtimes, services, and cloud-managed components. It shows each resource’s name, type, all detected versions, and how many entities were identified running each version.