Choose the deployment
Use Hermetiq Cloud or the customer-managed dashboard and project supplied by your organization.
Set up Hermetiq, connect Bazel and Buildbarn data, and bring build intelligence into your engineering and AI-agent workflows.
Hermetiq’s in-product Quickstart generates the project-specific values and credentials your build needs. The public documentation explains the flow; Quickstart remains the source of truth for your exact endpoints and project ID.
Use Hermetiq Cloud or the customer-managed dashboard and project supplied by your organization.
Use Cloud Quickstart or your administrator-provided helper and endpoints to configure the Bazel workspace.
Run a build, then confirm it appears in Build History and open the relevant analytics views.
Choose the Hermetiq Cloud or customer-managed onboarding path, secure the project credential, configure Bazel, and verify your first build.
Find and group builds, inspect invocation evidence, compare runs, and interpret cache, profile, test, RBE, trend, and cost views.
Understand what Hermetiq receives from Bazel, remote cache, Buildbarn, profiles, OpenTelemetry, and configured cost sources.
Use project-scoped values from Quickstart for BEP ingestion, authentication, profiles, metadata, remote cache, and build grouping.
Connect CAS and Bytestream, completed-action and cache telemetry, invocation logs, BEP forwarding, OpenTelemetry, and cost data.
Connect Bazel to a managed or customer-managed executor, configure platform properties and authentication, and verify remote actions.
Install the Hermetiq skill and MCP server for Claude Code, Claude Desktop, Cursor, Windsurf, or Codex, then query real build data.
Manage projects, users, roles, machine credentials, and project integrations, and understand deployment-controlled retention.
Understand the hosted and customer-managed deployment paths, including identity, telemetry authentication, and data boundaries.
Resolve the most common setup, authentication, profile-ingestion, MCP, remote-cache, and Buildbarn integration problems.
Hermetiq joins the build graph to the cache, execution, infrastructure, profile, and cost signals that explain how a build behaved.
Build and invocation identity, targets, tests, timing, status, and build metadata.
Cache lookups, hits, misses, action keys, and available miss-reason analysis.
Queue, input-fetch, execution, output-upload, worker, and action-level context.
Build phases, critical path, parallelism, client pressure, and profile-derived insights.
Configured metrics, logs, and traces from Hermetiq, Buildbarn, Kubernetes, and supporting services.
Cost reporting and attribution where the relevant infrastructure data is configured.