# Pipemesh

> Pipemesh is a CI/CD control plane: one pipeline shows every deployment in flight and holds broken revisions back. Works with GitHub and GitLab; run jobs on our runners, yours, or GitHub Actions.

## Docs

- [Why Pipemesh](https://pipemesh.io/docs/why): Why a CI/CD control plane: one live view of every change moving toward production, promotion decided by rules you can trust, work that runs where you already run it — and how that compares with run-based CI, CI servers and deploy tools.
- [Getting started](https://pipemesh.io/docs/getting-started): The fastest way to start: let your coding agent set up Pipemesh with the Pipemesh skill. Then organizations, enabling repositories, writing pipemesh.yaml by hand, and watching revisions run.
- [The definition](https://pipemesh.io/docs/pipeline-yaml): The pipemesh.yaml definition: bodies, registration, triggers, inputs, types, job types, what a job checks out, workflow and pipeline jobs, GitHub Actions as an executor, matrix expansion, typed components, and editor validation.
- [Release flow](https://pipemesh.io/docs/release-flow): How revisions promote through a Pipemesh pipeline: approval cursors, trustworthy skips, consolidation and supersede, retries, structure changes.
- [GitHub integration](https://pipemesh.io/docs/scm-integration): GitHub App permissions, credentials, webhooks, native check runs on pull requests, and keyless job identity via OIDC.
- [Using the API](https://pipemesh.io/docs/api): API tokens, what each can do, and the REST endpoints behind every Pipemesh screen.
- [Bring your own runners](https://pipemesh.io/docs/runners): Register your own runner agents against a Pipemesh instance and route jobs to your own machines by queue.
- [Hosted runners](https://pipemesh.io/docs/hosted-runners): Pipemesh's runner fleet for untagged jobs: how it works, the compute limits, what a job runs in (Linux arm64 or amd64), and building images for both.

## Use cases

- [Turborepo monorepo with Vercel Remote Cache](https://pipemesh.io/docs/turborepo-monorepo): A Turborepo monorepo on Pipemesh: each revision reaches only the services its task graph says it can affect, deploys run only for a new bundle, and builds share Vercel Remote Cache with no stored key (OIDC).
- [Nx monorepo with Nx Cloud cache](https://pipemesh.io/docs/nx-monorepo): An Nx monorepo on Pipemesh: each revision reaches only the services whose Nx inputs changed, deploys run only for a new bundle, and builds share Nx Cloud's cache, written from the default branch only.
- [Bazel monorepo with BuildBuddy cache](https://pipemesh.io/docs/bazel-monorepo): A Bazel monorepo on Pipemesh: each revision reaches only the services whose Bazel targets it can change, deploys run only for a new jar, and builds share BuildBuddy's remote cache, written from the default branch only.
- [Several repositories, one pipeline](https://pipemesh.io/docs/multirepo): A pipeline that declares other repositories: every revision pins a commit of each, a push to any of them starts a revision, and a jar built from one repository is consumed by a job working in another.

## Legal

- [Terms of Service](https://pipemesh.io/docs/terms): The terms that govern the use of pipemesh.io.
- [Privacy Policy](https://pipemesh.io/docs/privacy): What Pipemesh collects, why, who else sees it, and for how long.