Install timoni with Homebrew, apk, MacPorts, Nix, zypper, scoop, winget

Project links

• Homepage
• Repository

Commands and aliases

• timoni

Project history

The project was created by Stefan Prodan and describes itself as powered by CUE and inspired by Helm. Its README frames the project as an attempt to improve Kubernetes configuration authoring by replacing Helm-style Go-template YAML and Kustomize-style YAML layering with CUE type checking, code generation, and validation.

Timoni's model deliberately maps familiar Helm concepts into a CUE/OCI vocabulary: modules correspond to charts, instances correspond to releases, and bundles correspond to umbrella charts. That made the project legible to Kubernetes operators while still giving package nerds a newer artifact and schema story to inspect.

Adoption history

The official docs show Timoni being distributed through Homebrew and used against OCI registries such as GitHub Container Registry. The supplied package-manager facts also show packaging across Homebrew, MacPorts, Nix, Scoop, winget, apk, and zypper, which indicates interest beyond the upstream tap even though the project remains young.

The project has continued regular prerelease-style development, with GitHub showing dozens of releases and v0.27.0 as the latest release on July 2, 2026. Its docs still warn that Timoni is under active development and APIs may change incompatibly, so adoption is best understood as early cloud-native tooling adoption rather than a fully settled ecosystem standard.

How it is used

Timoni is used from the CLI to apply, build, inspect, upgrade, and delete Kubernetes module instances. The quickstart demonstrates pulling a module from an OCI registry, applying it into a namespace, inspecting module metadata and digest, and later composing multiple instances with a CUE bundle file.

For GitOps users, Timoni can build Kubernetes manifests and push or hand them to Flux workflows. The official Flux interop docs also show Timoni bundles orchestrating Flux HelmRelease resources, giving users a bridge to existing Helm chart repositories.

Why package nerds care

Timoni matters to package-manager watchers because it treats Kubernetes app packaging as OCI artifacts plus CUE schemas, putting it near Helm, Carvel, Flux OCI, and CUE rather than traditional OS package managers. Its value is in the packaging model: signed, semvered modules distributed next to container images.

It is also a useful example of a modern CLI that appears in many package indexes early in its life, where package availability serves as a signal that platform engineers want repeatable installs even for fast-moving infrastructure tools.

Timeline

• 2024: Documentation site copyright and examples show Timoni's public docs and quickstart in active use.
• 2026: GitHub lists v0.27.0 as the latest release on July 2, 2026.

Related projects

• Helm is the most direct conceptual comparison; Timoni explicitly maps modules, bundles, and instances to charts, umbrella charts, and releases.
• CUE supplies the configuration language and type system that differentiates Timoni from YAML-template tools.
• Flux appears in Timoni's official GitOps and Helm-interoperability docs as a companion controller ecosystem.

Sources

• https://github.com/stefanprodan/timoni README: project purpose, Helm inspiration, CUE model, module/instance/bundle concepts, active-development warning.
• https://timoni.sh/ quickstart and home docs: OCI module workflow, bundle workflow, lifecycle features.
• https://timoni.sh/gitops-flux/ and https://timoni.sh/flux-helm-interop/: Flux and Helm interoperability usage.
• source_facts.package-manager: package availability across multiple package managers.