innventionhub

Inspiration

Software has GitHub — a shared home where every idea, no matter how small, gets version-controlled, forked, and improved by anyone willing to contribute. Physical invention has nothing like it. Inventors still work in isolation: sketches buried in notebooks, CAD files emailed back and forth, prototypes reinvented from scratch because no one could find or build on prior work. We wanted to bring the collaborative, iterative workflow that made open-source software explode to the world of physical invention.

What it does

InnovationHub is a version-controlled platform for physical and product inventions. Users create "repos" for their inventions and commit design iterations — sketches, CAD files, bills of materials, and test results — as the design evolves. Anyone can fork an invention to build their own variant, open issues to flag design flaws, and submit pull requests to propose improvements. Every invention carries a full, public history of who contributed what, and why.

How we built it

We started by mapping the core GitHub metaphor onto physical invention: repos became invention projects, commits became design iterations, and pull requests became proposed design changes with reviewable diffs. From there we designed the data model — repos, versions, files, issues, and contributors — and built the interface around three core workflows: publishing a new design iteration, forking an existing invention, and reviewing a proposed change. We prioritized a clean, minimal UI so the focus stays on the invention itself rather than the tooling.

Challenges we ran into

The biggest challenge was translating "diffs" from code to physical designs — a pull request in software shows line-by-line changes, but there's no equivalent standard for comparing two versions of a CAD file or a BOM. We had to design a simplified versioning model that captures meaningful change (dimensions, materials, test results) without requiring deep CAD-diffing tools. Balancing flexibility for different invention types (mechanical, electronic, product design) against a simple, consistent structure was also an ongoing tension throughout the build.

Accomplishments that we're proud of

We're proud of designing a coherent mental model that makes version control intuitive for non-developers — inventors who've never used Git can understand "fork this design" and "propose a change" without any onboarding. We also successfully built a working commit history and fork/merge flow that mirrors the software development experience inventors are trying to replicate for hardware.

What we learned

We learned how much of GitHub's power comes not from the tooling itself but from the shared cultural norms around it — attribution, forking etiquette, and public accountability. Recreating that for physical invention meant thinking as much about community design as software design. We also learned firsthand how much harder "diffing" is for physical objects than for text, and gained a much deeper appreciation for the tooling problem hardware creators face.

What's next for InnovationHub

Next, we want to add structured diffing for common file types (CAD, BOMs, schematics), integrate with 3D printing and fabrication services so a forked design can go straight to production, and build a reputation and credit system so contributors get provable recognition for their work — the hardware equivalent of a GitHub contribution graph.

Built With

• codex
• gbt5.6sol
• javascript
• python