---
title: Free To Paid Journey
status: current
last_reviewed: 2026-06-14
---

# Free To Paid Journey

The public path should be low-friction but not vague.

A curious user can inspect what Helm renders and try public catalog artifacts
without starting with a private production workflow. A ConfigHub user can then
upload, view, diff, scan, approve, and operate the rendered objects as Units.

The paid line is not "rendering YAML." The paid line is operational value:
private charts and repos, custom overlays, production target decisions, old
version patches, fleet promotion, bulk operations, policies, approvals,
private evidence, and managed support for hard lifecycle behavior.

The product story should lead with: use Helm charts, ship ConfigHub variants,
and keep hard changes visible.

## Authoritative Sources

- [Site journey](../../site/journey.html)
- [Offering](../../docs/user/offering.md)
- [What you get](../../docs/user/what-you-get.md)
- [Product support tiers](../../docs/user/product-support-tiers.md)
- [Maintenance strategy](../../docs/planning/maintenance-strategy.md)