Browse Docs
Catalog
Config
Stacks
Operate
Docs

Start free, then add an account or the commercial product

ConfigHub is free to start. Check and deploy a Catalog configuration with local tools. Add a free account to keep, change, and promote the result, then add the commercial product for private and production work.

You check and deploy for free, upload, release, and promote with an account, then govern with the commercial product. See the whole path on the Operate page.

Try Redis · Choose an example · Learn ConfigHub

1. See what is free, and what needs the commercial product

Pulling a public Catalog package is anonymous, so the first three rows need no ConfigHub account or registry login.

CapabilityFree, localFree accountCommercial
Browse the Catalog and pull a public packageYesYesYes
Render it locally and read the exact objectsYesYesYes
Deploy with your own kubectl, Flux, or Argo CDYesYesYes
Keep the reviewed result as shared, versioned configurationNoYesYes
Create environment, region, or customer variantsNoYesYes
Promote a change and publish a release OCINoYesYes
Use private charts, private values, or a custom catalogNoNoYes
Add teams, approvals, and policy gatesNoNoYes
Scan, patch, promote, and observe many applications at onceNoNoYes
Get production support, older-version support, or an SLANoNoYes

Payment starts at the first private or team need: a private chart, private values, a team approval, a fleet-scale operation, or a production support commitment.

The commercial product comes as a hosted service you sign up for yourself and as a standalone enterprise product; pricing for both is on request. Availability can differ between the two editions, so check with ConfigHub for current product, support, and policy details.

Sign up for ConfigHub or ask about the enterprise product. Follow the official ConfigHub tutorial for one component, a change, and a promotion to production.

The local tools work today. A hosted path without sign-in is planned rather than shipped. Run it with Flux, Argo CD, or kubectl shows what works without an account.

2. Check what exists today

Each count below covers the 245 recorded base variants, each tested on its own. The counts stay separate rather than adding up to a production claim.

113Catalog components · across 140 tested versions, each with its configuration and requirements recorded.
246/246Helm render matches · Helm and cub installer produced the same objects from the recorded settings.
198/246Stored in ConfigHub · The rendered objects were uploaded and checked as ConfigHub Units.
148/246Local Kubernetes runs · The configuration was applied to a local target and observed.
139/246OCI through GitOps · A GitOps controller pulled the reviewed OCI and reconciled it in a live run.

See what has been tested · Check one claim · See what is not ready yet

3. Send a missing or broken public chart

If the Catalog is missing a public chart or its output differs from Helm, send the chart and values that show the problem through the problem chart issue template. See the other paths for a chart the catalog does not have.

4. Read the supporting detail

These project records explain support, commercial planning, no-server work, and the limits of current claims.

Use the public paths first. Add ConfigHub when the configuration needs shared history, controlled change, promotion, or rollout.