Visual and semantic diffs
Review schematic and PCB changes in a browser-based workspace that uses base/head comparisons instead of raw KiCad syntax alone. The view is designed to show changed hardware objects, not just file lines.
KiHub
KiHub is a hardware review platform for KiCad projects. It helps teams review schematic and PCB changes in context using visual diffs, checks, pinned discussions, and traceable decisions connected to GitHub.
Hardware review workspace for KiCad projects
KiHub is a hardware review platform for KiCad projects. It adds a browser-based review workspace between KiCad authoring and a merge decision so teams can inspect changes in context instead of relying on file diffs alone.
The product is centered on review, not editing or repository hosting. KiCad remains the design tool, GitHub remains the source of truth, and KiHub layers in visual diffs, review checks, pinned discussions, and an auditable decision trail for schematic and PCB changes.
Teams can review a GitHub pull request automatically or compare any two revisions on demand, including branches, tags, and commits. The workflow is designed to make readiness signals such as ERC, DRC, BOM completeness, and design discussion visible in one place before a revision is approved.
KiHub also supports controlled sharing. Review links can be published as read-only pages, and the security model emphasizes repository-scoped access, temporary source processing, and no repository write access.
Core capabilities
Review checks and readiness gates
Surface ERC, DRC, schematic-to-PCB parity, BOM completeness, and project policy as part of the review process. Checks can appear as informational signals or required gates so reviewers can judge readiness before merge.
Pinned design discussions
Attach questions and requested changes to the relevant schematic sheet, component, footprint, route, or board location. Threads remain associated with the design context rather than a source-file line number.
Traceable review record
Keep a durable record of what changed, which checks passed, who approved the revision, and why it was ready to merge. Review activity and decision history stay attached to the revision.
PR and manual review workflows
Start from a GitHub pull request or compare any two revisions on demand, including branches, tags, and commits. KiHub keeps the review current as pull requests update and can also support manual comparisons without a PR.
Common review scenarios
Review a hardware pull request
Use KiHub when a pull request changes a schematic or PCB and the team needs to understand the impact before merging. Reviewers can inspect visual evidence, checks, and threads in one workspace instead of piecing together status from multiple tools.
Compare arbitrary revisions
Use the manual compare flow when you need to compare two revisions that are not already in a PR, such as a branch against a tag or a commit against another commit. This supports independent review of a specific hardware revision.
Discuss design changes in context
Use the review workspace when comments need to refer to a capacitor, connector, trace, footprint, or board area rather than a line in a source file. Pinned threads keep the discussion attached to the design context.
Evaluate readiness before merge
Use the checks view when approval depends on readiness signals such as ERC, DRC, schematic-to-PCB parity, BOM completeness, or project policy. The review record keeps these signals separate from the final merge decision.
Share a review externally or across teams
Use controlled read-only links when you want to share a review with stakeholders who should see the current review state but not edit, merge, or rerun checks. Links can be revoked and can expire.
Pros and Cons
Pros
- Shows KiCad changes in a hardware-aware browser workspace instead of relying on file diffs.
- Combines visual diffs, checks, discussion, and decision history in one review record.
- Supports both pull request reviews and manual comparisons across branches, tags, and commits.
- Uses a repository-scoped GitHub App and does not require repository write access.
- Can publish controlled read-only review links for sharing with others when needed.
Cons
- It is intentionally focused on review rather than editing, so it does not replace KiCad or GitHub.
- The site notes that support for legacy or mixed-version projects should be checked with the team before evaluation.
- Public review pages are read-only, so they are meant for sharing evidence rather than editing or merging.
FAQ
Does KiHub replace KiCad or GitHub?
No. KiHub is positioned as the review layer between KiCad and GitHub. Engineers keep designing in KiCad, and GitHub remains the repository and source of truth.
Which KiCad projects are supported?
KiHub works with modern .kicad_sch and .kicad_pcb projects. The repository’s toolchain is selected when you connect it, and the site recommends contacting KiHub before evaluating a legacy or mixed-version project.
What GitHub access does KiHub need?
KiHub uses a GitHub App with read access to repository contents, pull requests, metadata, and relevant organization membership events. It can publish review status back to pull requests through GitHub Checks, but it does not need repository write access.
What happens to private design files?
Original KiCad source files are processed temporarily to generate review models and artifacts, then removed from active processing storage after processing is complete.
How do public review links work?
Public review links are accessible to anyone with the link, are read-only, and can be revoked or given an expiration date. KiHub does not publish pull request reviews or manual compare reviews automatically; a user must create the link.
Quick Facts
- Category
- Hardware review platform
- Primary users
- Hardware teams working on KiCad projects
- Workflow
- GitHub pull request reviews and manual branch, tag, or commit comparisons
- Integration model
- GitHub App with repository-scoped read access
- Supported project types
- Modern .kicad_sch and .kicad_pcb projects
- Pricing status
- Free for public repositories; private repositories are free during beta
Alternative a KiHub
ByteAsk
ByteAsk is a terminal-first AI coding agent for C and C++ that edits repositories and verifies changes with the real compiler, debugger, sanitizers, and tests before showing a diff. It offers a free tier plus paid plans, with editor connectors and zero-retention handling described in the source.
hob
hob is an independent workspace for coding agents that keeps agent sessions, terminals, history, and follow-up work organized around the tools and providers you already use. It is aimed at developers who want local control over routing, history, and workspace structure rather than a bundled model stack.
Manta AI
Manta AI is an autonomous web app testing tool for teams that want to map application behavior, catch regressions, and generate tests without writing scripts or maintaining selectors. It works from a URL and supports plain-English test flows, run results with screenshots, and scheduled or deployment-triggered checks.
CreateOS Sandbox
CreateOS Sandbox is an isolated compute environment for running code and agent workloads inside Firecracker micro-VMs. It is designed for workflows that need machine-level isolation, private networking between sandboxes, and programmatic control through SDK, CLI, or MCP.
Biji
Biji è una piattaforma versatile progettata per migliorare la produttività attraverso strumenti e funzionalità innovative.
Ably Chat
Ably Chat is a chat API platform for building custom realtime chat applications. It supports room-based messaging, typing indicators, presence, reactions, and message updates, with usage-based pricing options for different deployment stages.