Harness Open Source
Harness’ self-hostable, all-in-one developer platform — source control, CI/CD pipelines, hosted developer environments, and an artifact registry in one binary (Apache-2.0, Go, ~37,660★/3,301 forks; created 2014-02-07, last pushed 2026-08-03). The repo is the former Gitness, and it absorbed Drone (the README’s “Where is Drone?” section folds the long-running Drone CI project into this platform). Routed here 2026-08-05.
What it is, and the corner it opens
This spoke listed build & CI as an owned topic but had only ever held it obliquely — monorepo scaling (block-monorepo-migration) and version control (git, lore) — never a CI/CD system as the subject. Harness Open Source is that: pipelines defined as YAML, run in Docker, gated by approvals, beside a Git host and a container/artifact registry. It fills the CI corner and adds two the spoke had not named — hosted dev environments and artifact registries.
Its defining bet is consolidation. Git hosting, CI, dev environments and registry are usually four tools from four vendors; this is one self-hosted binary spanning the whole commit → build → store → deploy path. That is the same shape as monorepo: collapse many boundaries into one managed thing and pay for it with a platform to run, moved up from the repo layout to the delivery stack.
The homonym, and the cross-wiki seam it exposes
“Harness” here is the company, not an agent harness — the same warning harness-io already carries in agentic-tooling-wiki, where the company appears for its AI-agent delivery product (Autonomous Worker Agents, AI Agent DLC — treating an agent as one more governed step in a pipeline).
The two are worth reading together. The commercial pitch over there is governance for agents that ship code; the thing under it, the pipeline that does the shipping, is this open-source platform. So the seam is one company at two layers: the delivery machinery lives here (dev-tooling), the agent governance sold on top lives in agentic-tooling. Cross-linked, not duplicated.
Where it stops being this spoke’s business
The operation of a Harness deployment in production — SLOs, incident response, keeping the
pipelines up — is ../platform-ops-wiki. This page is the tool as build/ship infrastructure: what
it is and what it consolidates. The boundary is the standing dev-tooling ↔ platform-ops line (building
the pipeline vs running it), and it holds cleanly here.
Caveats
- Open-core. This is the free tier of a commercial platform; the hosted Harness product has capabilities this repo does not, and the README’s framing is a vendor’s. T2 for that reason — first-party and interested, though the platform’s scope (SCM/CI/registry/environments) is verifiable from the repo itself.
- Star/fork counts and the Drone-absorption state are a 2026-08-05 snapshot.
Related
harness-io · git · monorepo · block-monorepo-migration · developer-tooling · synthesis