Kargo Promotion Stages Deserve Their Own Exposure Inventory

Kargo orchestrates continuous promotion between stages and hands deployment work to a GitOps agent. A promotion can change desired state across environments, which makes the control plane more than a read-only dashboard.

The word Kargo also appears in logistics, shipping, and unrelated products. ZoomEye counts for a bare app or title need product-specific context before they can support a Kargo inventory.

Promotion is an authority

Kargo's core model centers on stages and promotions. A stage is a promotion target, and a promotion process changes the desired state that a GitOps agent later reconciles. A Stage can have a promotion template with steps that update a repository, render manifests, and trigger synchronization.

The Kargo API-token documentation describes programmatic access to Kargo APIs and project-scoped roles. A token created for a CI job can therefore initiate or observe promotions. The role, project, and allowed actions matter more than the token's display name.

The dashboard provides a useful audit view of promotions, verification results, freight history, and live manifests. A public or weakly authenticated view can disclose application versions, repository paths, environment names, and operational state.

Broad title evidence

On 2026-11-04 at 20:49 UTC, a count-only ZoomEye SDK query returned 0 for app="Kargo" and 2,103 for title="Kargo". The product-scoped query title="Kargo" && (http.body="kargo.io" || http.body="kargo.akuity.io") returned 0 at 20:50 UTC.

The title count is not usable as a Kargo deployment count. It is a broad lexical match. The scoped result suggests that this exact domain combination did not appear in the title-matching records at that time, but the query did not retrieve records and cannot prove absence.

This is a good example of why titles alone are dangerous inventory metrics. A target query should include a product-specific application fingerprint, vendor-controlled page metadata, or an endpoint shape that the owner has validated. Even then, public search confirms a web surface, not the number of promotion pipelines.

Map stages and credentials

List Kargo projects, stages, warehouses, channels, promotion policies, and API tokens. For each stage, record the target Git repository, the credentials used by promotion steps, the verification policy, and the humans or service accounts allowed to promote.

Check that a project role cannot promote into another project. Review the secrets available to promotion steps and whether a template can read a broader credential than the step needs. Confirm that the GitOps agent's synchronization permission is limited to the intended repository and environment.

Test a promotion with a read-only token. Attempt a stage change in another project. Disable a webhook or notification channel and confirm that promotion behavior and audit records remain clear.

The internet measurement is a lead list. The real Kargo inventory lives in the Kubernetes resources and the credentials attached to promotion steps. Treat the stage graph as an authorization graph.