CDviz

Appearance

CDviz vs Kargo ​

Comparing CDviz and Kargo for environment promotion and delivery visibility? These two open-source tools overlap on one headline use case — promoting artifacts through environments — but belong to different categories and are often complementary rather than alternatives.

Full disclosure: Kargo was one of the inspirations for CDviz's event reaction and artifact-lifecycle observability. The difference is the approach: Kargo is a promotion control plane you adopt as part of your delivery machinery; CDviz observes the tools you already run and can trigger automation from their events — without replacing anything.

Last updated July 2026. Corrections welcome.

At a glance ​

CDvizKargo
LicenseApache 2.0Apache 2.0
CategorySDLC observability + event reactionContinuous-promotion control plane
Made byCDvizAkuity (creators of Argo)
Self-hosted✅✅
Commercial offering✅ Cloud €20/mo · Pro €200/mo✅ Kargo Enterprise (Akuity)
CDEvents standard✅ native❌
ScopeAny SDLC tool (CI, CD, registries, incidents…), Kubernetes or notKubernetes delivery with GitOps (Argo CD)
Promotion execution⚠️ delegates to your workflow engine via event reaction✅ native (Warehouses → Freight → Stages)
Requires adopting a new delivery model❌ listens to your existing tools✅ model your pipelines as Kargo CRDs
Artifact lifecycle visibility✅ cross-tool, from events (Artifact Timeline)✅ within Kargo-managed pipelines
DORA metrics & SDLC dashboards✅❌
Verification gates before promotionvia your workflow engine (e.g. Argo Workflows)✅ built-in (analysis / verification steps)

Key differences ​

  • Orchestrate vs observe-and-trigger: Kargo is the promotion engine — you define Warehouses (artifact sources), Freight (a versioned bundle of image + commit + config), and Stages (environments with gates), and Kargo executes promotions by writing to Git for Argo CD to sync. CDviz doesn't execute promotions itself: it collects CDEvents from your toolchain and its event reaction sinks trigger the engine you already have — Argo Workflows, your CI, or even Kargo.
  • Adoption cost: Kargo asks you to model each delivery pipeline in its CRDs and run it as part of your control plane — powerful, but a real migration for existing pipelines. CDviz plugs into what you run today via webhooks and sinks; nothing about how you deploy has to change.
  • Scope: Kargo is focused on Kubernetes delivery with GitOps, and shines there. CDviz covers the whole SDLC — source, CI, artifacts, deployments, tests, incidents — across Kubernetes and everything else, normalized to the open CDEvents standard.
  • Visibility model: Kargo's UI shows where each Freight is across its own Stages — excellent, but scoped to pipelines Kargo manages. CDviz builds artifact timelines, DORA metrics, and dashboards from events across all your tools, including deliveries Kargo never sees.
  • Analytics: CDviz ships DORA, pipeline reliability, test results, and incident dashboards. Kargo has no analytics ambitions — it is promotion machinery, not an observability product.

Better together ​

The two compose naturally rather than compete:

  • Kargo → CDviz: emit a webhook from Kargo promotion / verification phases (or from the Argo CD syncs it drives) into the CDviz collector, and Kargo-managed deliveries join your cross-tool timelines and DORA metrics.
  • CDviz → promotion: where you haven't adopted Kargo, CDviz event reaction covers the promotion trigger — e.g. testSuiteRun.finished in staging fires an HTTP sink that submits a promotion workflow.

When to choose CDviz ​

  • You want visibility (timelines, DORA, dashboards) across a heterogeneous toolchain — not only Kubernetes.
  • You want to trigger promotions and other automation from delivery events without replacing or re-modeling your existing pipelines.
  • You are adopting the CDEvents open standard.
  • You need SDLC analytics: DORA metrics, pipeline reliability, test results, incident tracking.

When to choose Kargo ​

  • You deploy on Kubernetes with GitOps (Argo CD) and want a dedicated, opinionated promotion engine.
  • You want built-in guardrails: verification gates, approvals, and a UI showing exactly which version runs where.
  • You're prepared to model your delivery pipelines as Kargo Stages and let it own promotion execution.

Summary ​

Kargo and CDviz solve different problems that meet at "promotion". Kargo is the better promotion executor for Kubernetes/GitOps shops willing to adopt its model. CDviz is the better observer and connector: it gives you artifact lifecycle visibility and event-driven automation across your whole toolchain without asking you to replace anything — and it will happily observe (or trigger) Kargo too.

Get started with CDviz

Self-host CDviz — free, Apache 2.0. Or try CDviz Cloud — €20/mo, 14-day free trial, no credit card.

FAQ ​

Is Kargo an alternative to CDviz? Mostly no — they're different categories. Kargo executes multi-stage promotions on Kubernetes; CDviz observes your SDLC and reacts to its events. They overlap only if promotion triggering is the sole thing you need.

Can CDviz do promotions like Kargo? CDviz can trigger a promotion — an event like "tests passed in staging" fires a sink that starts your promotion workflow (Argo Workflows, CI job, custom service). It is not a promotion control plane: no Freight/Stage model, no built-in promotion UI or gates. If you need those, use Kargo (possibly alongside CDviz).

Does Kargo emit CDEvents? Not natively. Kargo-driven deliveries can still reach CDviz via webhooks from Kargo, Argo CD, or your CI, mapped to CDEvents by the collector.

Is CDviz free? Yes — the Community plan is free forever (Apache 2.0, infrastructure costs only). Cloud (€20/month) adds managed hosting; Pro (€200/month) adds extra integrations and support. Both are billed per organization, not per seat.