TrueCharts: A Community Helm Chart Catalog Built for Interoperability
Community Helm Chart Repository. title: TrueCharts Community Helm Chart Catalog** TrueCharts is a catalog of highly optimised Helm Charts.
At a glance
- What is it?
- TrueCharts is a community-driven catalog of Helm charts designed to work together, targeting users of any Helm-compatible deployment tool. Its value lies in consistency and tuning options, but its AGPL-3.0 license and distributed development model require careful evaluation.
- Who is it for?
- Adopt TrueCharts if you run a Kubernetes cluster with Helm and want a large, community-curated set of charts that are designed to be consistent and interoperable, especially if you value permissive tuning over strict upstream defaults. Do not adopt it if your organization cannot accept AGPL-3.0 obligations for chart code, or if you need a single vendor with a centralized roadmap and formal support guarantees.
- Can I use it commercially?
- Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly Go Template, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 14, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
The Problem TrueCharts Solves and Its Target User
TrueCharts addresses a common pain point in the Kubernetes world: Helm charts from different sources often have inconsistent conventions, making them difficult to deploy together. The project's README states that all its charts are "supposed to work together" and be easy to set up using any Helm-compatible deployment tool. This is aimed at the average user who wants more than enough options to tune things to their liking, without being a Helm expert. The target audience is community members running self-hosted applications on Kubernetes, who value a catalog where charts share a common design philosophy. The project is not for enterprises seeking commercial support or a formal SLA, as the README emphasizes a community-driven model with support via Discord and issues.
How the Catalog Is Structured and Maintained
The repository is a community Helm chart catalog, with the primary language listed as Go Template, which is the templating language used in Helm charts. The catalog is not a single application but a collection of charts, each presumably following a common set of templates and conventions. The README describes the development process as "fully distributed and agile," where each chart maintainer sets their own roadmap and speed, and does not have to comply with a centralized roadmap. This means the catalog is a federation of independently maintained charts, which can lead to inconsistencies in update frequency and quality. The project uses pre-commit and Renovate for automation, as indicated by badges in the README, which helps keep charts up to date and linted. The actual mechanism for installing charts is via Helm, with the repository serving as a source for `helm install` commands, though the README does not provide explicit installation commands.
Getting Started: Commands and Configuration
The README does not include explicit Helm commands, which is a gap for new users. However, based on standard Helm practice, you would add the TrueCharts repository using `helm repo add truecharts https://charts.truecharts.org` and then install a chart with `helm install my-release truecharts/<chart-name>`. The exact URL is not given in the README, but the homepage points to truecharts.org, where the manual and FAQ are located. The README directs users to the website for more information on creating charts, and to the FAQ and manual for support. Configuration is done through Helm values, and the charts are designed to be tunable, as the README promises "more than enough options to tune things to their liking." Since the material does not provide a concrete example, you must consult the website for the current repository URL and chart names.
A Real Limitation: Distributed Maintenance and Version Churn
The most significant limitation is the lack of a centralized roadmap. While the README celebrates this as freedom, it means chart maintainers can update their charts at different paces, potentially leading to breaking changes or inconsistent support across the catalog. The recent releases show a major version jump from v2.0.0-BETA-17 to v2.0.0 and then v2.0.6, which suggests active development but also potential instability. Users who rely on a stable, predictable catalog may find this churn problematic. Additionally, the README's support model relies on community channels like Discord and the issue tracker, which may not offer timely or guaranteed responses. This is the wrong tool for a production environment that requires formal support and versioned release guarantees.
Licence and Maintenance Costs
TrueCharts is licensed under AGPL-3.0, which is a strong copyleft license. This has implications if you modify the chart templates or distribute them. The license is not permissive like Apache-2.0 or MIT, so you must be aware of your obligations under AGPL-3.0, particularly if you offer the charts as a network service. The maintenance cost is twofold: you must track chart updates from multiple maintainers, and you must comply with the license if you redistribute modified charts. The project uses Renovate to automate dependency updates, which helps reduce the burden of keeping charts current, but the distributed nature means you cannot rely on a single release train. Before adopting, review the AGPL-3.0 license text and consider whether your use case triggers its conditions.
Alternatives and How They Differ
A direct alternative is the Bitnami catalog, which offers a large set of Helm charts but under a more permissive Apache-2.0 license. Bitnami charts are known for their consistency and centralized maintenance, with a single vendor (VMware) providing updates and support. This contrasts with TrueCharts' community-driven, decentralized approach. Another alternative is the official Helm charts repository, which is curated by the Helm community but has a narrower set of charts. The key difference is governance: Bitnami offers a centralized roadmap and commercial support options, while TrueCharts relies on volunteer maintainers. If you need predictable updates and legal simplicity, Bitnami may be a better fit. If you prefer a community-driven catalog with a focus on interoperability, TrueCharts is unique.
Who Should Adopt It and What to Verify First
TrueCharts is suitable for hobbyists and small teams running Kubernetes clusters who want a wide selection of charts that work together, and who are comfortable with community support via Discord and issues. It is not for enterprises that require formal support or a single point of accountability. Before adopting, verify the current state of the catalog on the TrueCharts website, check the issue tracker for any unresolved problems, and confirm that the charts you need are actively maintained. Also, review the AGPL-3.0 license to understand your obligations if you modify or distribute charts. Finally, test a chart in a non-production environment to ensure it works with your Helm setup, as the README does not provide a quick-start command.
Editorial conclusion
Adopt TrueCharts if you run a Kubernetes cluster with Helm and want a large, community-curated set of charts that are designed to be consistent and interoperable, especially if you value permissive tuning over strict upstream defaults. Do not adopt it if your organization cannot accept AGPL-3.0 obligations for chart code, or if you need a single vendor with a centralized roadmap and formal support guarantees. Before adopting, verify the current chart availability and maintenance status on the TrueCharts website and Discord, and review the AGPL-3.0 license text to understand your compliance duties, particularly if you modify or distribute charts. Also check the issue tracker for any unresolved breaking changes in recent releases like v2.0.0.
Community notes