Supply chain
One versioned OCI chart that pins every first-party image by digest at package time, so a version is an exact reproducible deployable. Installs on-prem and air-gapped.
The product is one self-contained umbrella Helm chart, published as a versioned OCI artifact:
ghcr.io/zeroroot-ai/charts/gibson:X.Y.Z
It carries the CRDs, the operators, and the workloads as ordered dependencies. It also carries the secret-sync resources, bringup jobs, and database cluster.
A version is a pin
The chart's values pin every first-party image by digest at package time. The chart version is therefore not a label that points at the most recent build. It names an exact set of image digests.
What that gets you:
- One string answers "What is running in production" exactly.
- When you install the same version twice, you get the same bits.
- To roll back, pin the previous version. That is one line, deterministic, with no rebuild and no question about what you go back to.
Promotion is a one-line version bump, in one direction, after the previous environment is green. No rebuild promotes anything.
Everyone installs the same artifact
The hosted fleet, ephemeral environments, and a customer who self-hosts all
install the same chart. The consumers are helm install, Argo, and Flux.
The GitOps tool consumes the artifact. It is never the unit of deployment.
What that gets you: the artifact you self-host is the artifact we test. It is not a re-derived approximation of it. A difference in behavior between your install and ours is a configuration difference, not a build difference.
On-prem and air-gapped installs
Federal, on-prem, and air-gapped customers install the same chart everyone else installs. There is no separate package and no second artifact to keep in step.
- Every first-party image is pinned by digest at package time, so the install is reproducible inside a perimeter that never reaches our registry.
- An air-gap image list ships with the chart. It names every image the chart pulls, and the operator mirrors each one into their own registry before installing. The list is generated from the chart. A CI job fails the build when it goes stale, so it cannot fall behind what the chart deploys.
- No GitOps controller is assumed.
helm installworks, and so does your own Argo or Flux. You pin the chart version wherever you declare it. - No service mesh is assumed. The chart does not require Istio. It carries its own Envoy and SPIRE auth edge.
The air-gap list lives at
airgap/ in the
charts repository.
We hold the chart to these constraints. They are not claims made after the fact.
What to check
- The chart version pins image digests, so two installs of one version match.
- Rollback is a version pin, not a rebuild.
- Self-hosted and hosted install the same artifact.
- The chart imposes no service mesh.
- The air-gap image list matches the chart, enforced in CI.
Audit
The platform records every model call with its full transcript inside your tenant. Every mission is replayable from its event timeline. No third-party trace vendor sits on the path.
Deployment
Run the whole stack on your own Kubernetes cluster, bring your own model keys, and choose who owns the isolation boundary.