KiHub is a hardware review platform for KiCad projects. Compare schematic and PCB revisions, discuss changes with pinned comments, run automated checks, manage approvals, and keep a traceable review history — without changing your Git workflow.
I’m building KiHub because there’s still a big gap in the way hardware changes get reviewed.
KiCad projects can live in Git and move through GitHub, but reviewing what actually changed is often surprisingly manual: opening KiCad locally, comparing revisions yourself, passing screenshots around, and discussing design decisions across GitHub comments or Slack.
KiHub adds the missing review layer around that workflow.
With KiHub you can:
Compare schematic and PCB revisions visually — see design changes in the browser instead of interpreting raw KiCad file diffs.
Start reviews automatically or on demand — from a GitHub pull request or by comparing any two branches, tags, or commits.
Discuss changes in context — leave threaded comments pinned directly to a schematic sheet or PCB location.
Run hardware-aware checks — including ERC, DRC, schematic-to-PCB parity, BOM completeness, and release readiness.
Set review and merge gates — decide which checks are informational and which must pass, and use review status and hardware checks to gate GitHub merges.
Review BOM impact — compare component changes, find missing data, and track order readiness.
Share reviews outside the workspace — publish read-only links for teammates or external reviewers.
Keep every decision traceable — preserve compared revisions, check results, discussions, decisions, and activity in one place.
KiCad stays the editor, and GitHub stays the source of truth. KiHub is the shared workspace where the hardware review happens.
If you’d like to explore it without connecting a repository, we have a gallery of live, read-only reviews generated from public KiCad projects:
I’d especially love feedback from people working with KiCad or reviewing PCB designs today: how does your team currently review hardware changes, and what part of that process is the most painful?
Thanks for checking it out!
About KiHub on Product Hunt
“Hardware review platform for KiCad projects”
KiHub launched on Product Hunt on August 19th, 2026 and earned 93 upvotes and 3 comments, placing #15 on the daily leaderboard. KiHub is a hardware review platform for KiCad projects. Compare schematic and PCB revisions, discuss changes with pinned comments, run automated checks, manage approvals, and keep a traceable review history — without changing your Git workflow.
On the analytics side, KiHub competes within Hardware, Developer Tools and GitHub — topics that collectively have 571.6k followers on Product Hunt. The dashboard above tracks how KiHub performed against the three products that launched closest to it on the same day.
Who hunted KiHub?
KiHub was hunted by Andrei Man. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of KiHub including community comment highlights and product details, visit the product overview.
Andrei Man
Hey Product Hunt 👋
I’m building KiHub because there’s still a big gap in the way hardware changes get reviewed.
KiCad projects can live in Git and move through GitHub, but reviewing what actually changed is often surprisingly manual: opening KiCad locally, comparing revisions yourself, passing screenshots around, and discussing design decisions across GitHub comments or Slack.
KiHub adds the missing review layer around that workflow.
With KiHub you can:
Compare schematic and PCB revisions visually — see design changes in the browser instead of interpreting raw KiCad file diffs.
Start reviews automatically or on demand — from a GitHub pull request or by comparing any two branches, tags, or commits.
Discuss changes in context — leave threaded comments pinned directly to a schematic sheet or PCB location.
Run hardware-aware checks — including ERC, DRC, schematic-to-PCB parity, BOM completeness, and release readiness.
Set review and merge gates — decide which checks are informational and which must pass, and use review status and hardware checks to gate GitHub merges.
Review BOM impact — compare component changes, find missing data, and track order readiness.
Share reviews outside the workspace — publish read-only links for teammates or external reviewers.
Keep every decision traceable — preserve compared revisions, check results, discussions, decisions, and activity in one place.
KiCad stays the editor, and GitHub stays the source of truth. KiHub is the shared workspace where the hardware review happens.
If you’d like to explore it without connecting a repository, we have a gallery of live, read-only reviews generated from public KiCad projects:
👉 Explore the KiHub demo gallery
I’d especially love feedback from people working with KiCad or reviewing PCB designs today: how does your team currently review hardware changes, and what part of that process is the most painful?
Thanks for checking it out!