Already running Buildbarn? Hermetiq is the chart + intelligence layer
Hermetiq maintains the Apache-2.0 Helm chart for Buildbarn and the intelligence layer that reads it. Artifact Hub lists that chart under the Hermetiq organization as a verified publisher. Barn Owl and Build Analytics turn queue, cache, and failure telemetry into explanations and reviewable fixes.
That is the expert path for a team that already operates Buildbarn. A BuildBuddy-style purchase adopts that vendor’s cache, execution service, and topology. Hermetiq is not that swap. The chart is the maintained Buildbarn install. The intelligence layer investigates the cluster. Managed Builds is how Hermetiq supplies cache and execution on that same stack when you want the cluster run for you.
Three jobs. Three Hermetiq layers.
The chart, the intelligence layer, and Managed Builds answer different questions. They are not three names for one platform swap.
The chart Hermetiq maintains
The chart packages Buildbarn remote cache and remote execution for Bazel on Kubernetes. The upstream project publishes example deployments rather than a maintained Helm chart. Hermetiq publishes and maintains this one, Apache-2.0, with source in Hermetiq/hermetiq-k8s.
Install commands, chart versions, architecture, and values change when the chart changes. Read them on the Buildbarn Helm chart page, the chart README, and Artifact Hub.
The intelligence layer on that cluster
Build Analytics & AI investigates the Buildbarn your team operates. Barn Owl is the AI build engineer in that product. Connect Bazel build events and the queue, cache, worker, storage, and failure signals your deployment exposes. Barn Owl explains what changed and proposes fixes as pull requests you review. Investigate in Hermetiq, or give your coding agent the same evidence through MCP.
Cloud Intelligence hosts that service. On-Prem Intelligence runs it in your environment. Your team still operates the cluster. Hermetiq does not take the pager for storage, scheduling, or workers unless the agreement is Managed Builds.
When Hermetiq should run the cluster
Managed Cache & Execution is Managed Builds. Hermetiq supplies the remote cache and the executors, and Build Analytics & AI is included. Cloud Managed Builds runs in Hermetiq Cloud. On-Prem Managed Builds runs in your environment. Agree the workload, the deployment, and who operates it before provisioning.
Choose Managed Builds when you want that operating scope from Hermetiq. The chart does not operate the cluster for you, and the intelligence layer does not replace it.
FAQ
What is the Buildbarn Helm chart for?
It is the Apache-2.0 Helm chart Hermetiq maintains for Buildbarn remote cache and remote execution on Kubernetes. Use it when your team operates that cluster. The upstream Buildbarn project publishes example deployments rather than a maintained Helm chart. Artifact Hub lists Hermetiq’s package as a verified publisher, and the source is in Hermetiq/hermetiq-k8s. Install commands, versions, architecture, and values stay on the chart page, the chart README, and Artifact Hub, because they change when the chart changes.
What is the intelligence layer?
Build Analytics & AI is the investigation product for a Buildbarn cluster your team operates. Barn Owl is the AI build engineer in that product. It uses Bazel build events and the queue, cache, worker, storage, and failure signals you connect, explains what changed, and proposes fixes as pull requests you review. Investigate in Hermetiq, or give your coding agent the same evidence through MCP. Cloud Intelligence hosts the service. On-Prem Intelligence runs it in your environment. On this path Hermetiq does not take the pager for storage, scheduling, or workers.
What are Managed Builds and Managed Cache & Execution?
They are one offering. Managed Cache & Execution is the product name. The docs call it Managed Builds. Hermetiq supplies the remote cache and the executors, and Build Analytics & AI is included. Cloud Managed Builds runs in Hermetiq Cloud. On-Prem Managed Builds runs in your environment. Provisioning, support, and day-to-day responsibilities are agreed before that cluster is provisioned. Choose it when you want Hermetiq to operate cache and execution. It is a different scope from the chart and from Intelligence.
Which should a team that already runs Buildbarn use?
Use the Helm chart to install and run Buildbarn. Add the intelligence layer when that cluster’s queue, cache, and failures should turn into reviewable fixes. Choose Managed Builds when Hermetiq should supply and operate cache and execution as well. Hermetiq is the chart maintainer and the intelligence layer for Buildbarn, not a second platform you swap onto. A BuildBuddy-style purchase adopts that vendor’s cache, execution service, and topology. Managed Builds stays on Buildbarn, with Hermetiq running it.
Where the chart stays current
- Artifact Hub — the published chart, from the verified Hermetiq publisher
- Chart README — install and values in Hermetiq/hermetiq-k8s
- hermetiq-k8s — repository README
- Buildbarn Helm chart — the page that carries install, architecture, and values
- Deployments — Cloud and On-Prem, Managed Builds and Intelligence
Start from the layer you need
Open the chart for the maintained Buildbarn install. Book a demo if you want the intelligence layer or Managed Builds scoped to your cluster. Build Analytics & AI is the product page for Barn Owl.