Buildhound
Buildhound turns Macs and Linux machines a team already owns into clean, single-use GitHub Actions runners. It is designed for coding-agent-driven teams: jobs run in fresh virtual machines on the team's hardware first, with GitHub-hosted runners as fallback.
At a Glance
- GitHub Actions teams
- Mobile and Apple-platform development teams
- Startups and engineering teams using Claude Code, Codex or Cursor
- Organisations with spare Mac minis, Apple-silicon Macs or Linux KVM machines
- +1 more
AI Tools by Buildhound
(1)
Buildhound
Self Hosted GitHub Actions Runners
Discussions
No discussions yet
Be the first to start a discussion about Buildhound
Latest News
Security release added server-side human approval for trusted machines, private caches for secret-bearing jobs and related security fixes.
Linux hosts launched, supporting Debian/Ubuntu KVM machines and Firecracker microVMs for Linux jobs.
Buildhound's CLI, MCP server, rules, cost model and documentation became publicly available in an MIT-licensed GitHub mirror.
Routing pull requests launched through the CLI and MCP, moving eligible jobs to connected machines while retaining GitHub-hosted fallback.
Products & Services
Control plane and dashboard that connect owned Macs/Linux machines to GitHub Actions, route jobs to available machines, provide failover to GitHub-hosted runners, and track jobs, savings, audit events and machine trust.
npm CLI for CI cost scanning, workflow estimates, pull-request fixes, machine connection, image building, routing, failover, job/account views, billing and setup. It emits JSON for agents and readable text in terminals.
MCP server exposing the CLI's CI-report, runner, routing, account, billing and audit operations as tools for Claude Code, Codex and Cursor.
Signed and notarised Apple-silicon menu-bar app for viewing what is running on a Mac, pausing it and opening settings; the agent can run without the app.
Market Position
Buildhound positions itself between plain GitHub self-hosted runners and hosted runner vendors. Its differentiators are using hardware the team already owns, fresh VM isolation per job, GitHub-hosted fallback, agent-first setup and flat per-machine pricing. The official comparison pages identify GitHub-hosted runners, Blacksmith, Depot, WarpBuild, Namespace, Ubicloud, StarSling, Vercel Daemons, Bitrise Build Hub, RunsOn, Cirun, AWS CodeBuild, Xcode Cloud, Manzanita, MacRun, Codemagic, CircleCI, Buildkite, ushr and Actions Runner Controller as alternatives or competitors.
Leadership
Founders
Beny Dishon K
Solo software engineer and creator based in Chennai. His personal site says he works as a software engineer at Maxapp GmbH, previously interned at Veryon, and builds products end to end with Next.js, TypeScript, Go, AWS and related tooling. GitHub identifies him as the sole public contributor to the Buildhound repository.
Executive Team
Beny Dishon K
Creator and solo developer
Software engineer based in Chennai; software engineer at Maxapp GmbH, formerly a Veryon software-engineering intern, and the sole public contributor listed on the Buildhound repository.
Founding Story
Buildhound began as Beny Dishon's solo product to make the computers teams already own useful for GitHub Actions without the drawbacks of a plain self-hosted runner. The initial vision combines agent-first setup, fresh per-job isolation, automatic routing/failover, and a flat per-machine price rather than per-minute billing.
Business Model
Revenue Model
Freemium subscription billed per connected machine, never per minute. Paddle is the merchant of record. Public repositories and one private repository on up to two machines are free; Pro covers private repositories and additional machines.
Pricing Tiers
Every public repository and one private repository on up to two machines, with every feature included.
Every private repository, unlimited connected machines, personal accounts and organisations; flat pricing, never per minute.
Annual billing, equivalent to $8 per machine per month; prices are before applicable tax.
Target Markets
- GitHub Actions teams
- Mobile and Apple-platform development teams
- Startups and engineering teams using Claude Code, Codex or Cursor
- Organisations with spare Mac minis, Apple-silicon Macs or Linux KVM machines
- Public open-source repositories and private repositories seeking lower CI costs
- Teams whose coding agents create more GitHub Actions work than hosted macOS capacity or included minutes can handle
- iOS/macOS builds and tests on owned Apple-silicon Macs
- Linux CI jobs on owned Macs or Linux KVM hosts
- Teams wanting clean VM isolation instead of a persistent plain self-hosted runner
- Repositories seeking to reduce GitHub-hosted runner costs
- Agent-driven repository setup and CI maintenance