Skip to content

Docs

Six pages, in the order the onboarding wizard uses them.

The same text your own agent reads on day one, inside the product, as the hive-docs knowledge collection. Written to be checked against the product rather than trusted — every claim names a call, a file or a status code.

The docs are published in English only.

  1. 01What Hive isHive runs jobs — CI/CD pipelines, test suites, builds, ad-hoc work — as Kubernetes Jobs across a fleet of clusters. A **run** is a DAG of **tasks**; each task executes in a container on whichever runner the scheduler picks.Read
  2. 02Onboarding checklistThe order below is the order the wizard uses, and it is not arbitrary: each step makes the next one possible.Read
  3. 03The GitHub App, then the projectHive talks to GitHub through a GitHub App installation — that is how it reads your code, posts commit statuses, and receives the webhooks that start runs. The App is public: you install it on your own account or organisation, and it issues a per-installation token scoped to the repositories you selected.Read
  4. 04Your first pipelineA pipeline lives at `.hive/main.star` in your repository. Starlark, not YAML.Read
  5. 05CredentialsThree separate things, needed at different times.Read
  6. 06Security and isolationWhat the tenant boundary actually gives you, stated so you can check it rather than trust it.Read