BoardRepo vs Hackaday.io for publishing a hardware project
Use Hackaday.io to tell the build story and reach its maker community. Use BoardRepo to keep the hardware source, saved versions and available board views together, with context your own assistant can read and a design you can continue in KiCad.
| Capability | Hackaday.io | BoardRepo |
|---|---|---|
| What a visitor sees first | The project story: description, details, build logs, instructions, photos, a components list, and who follows it. | The board: rendered schematic, PCB by layer, 3D model, BOM and the file tree. |
| Design files | Attached to the project as downloads, or linked out to a repository. | Uploaded as the project folder and rendered from the sources. Retained project files stay downloadable per published version; review upload exclusions before saving. |
| Opening the schematic or layout | Download the files and open them in the design tool, or rely on the PDFs and images the author posted; those are the file types with a preview. | Available KiCad and converted Altium views in the browser. Public boards need no account; restricted boards need access proof. Other formats are stored and downloadable. |
| Bill of materials | A hand-maintained components list with quantities. | Extracted from the design, filterable, and downloadable as CSV; components are indexed for search. |
| Version history | Build logs record the story over time; files are replaced or re-uploaded. | Numbered source versions, restore and visual comparison of supported published pairs; comparison needs sign-in and compatible ready renders. |
| Community | Followers, skulls, comments, Hack Chat, contests and a large maker audience. | Comments and saves on a board, and an open library browsable by component and tag. Not a social network. |
| Private and team work | Private projects, and team members who can update the project and its logs. | Token-bearing unlisted links, passwords, personal private boards and organization board grants. Team setup is through contact; connected assistants use separately approved access and current board permissions. |
| Machine readers | Web pages, and a public read-only API for projects, logs and components. | A markdown twin of every public board page for assistants and crawlers, and an MCP server for your own AI. |
| Cost | Free. | Personal core features are free. Team organizations use custom pricing. |
What Hackaday.io does well
A project page with build logs is the best way to explain a design: the dead ends, the measurements, the photo of the first board working. The audience is there, the contests bring attention, and a good log is read for years. None of that is what a design file viewer does, and BoardRepo does not try to.
Where the design files end up
The gap is the moment a reader wants to look at the actual schematic. On a story site the files are attachments: a zip to download and open in a tool the reader may not have, or a link to a repository that shows the schematic as text. On BoardRepo the same zip becomes a page with the schematic, PCB, 3D model and BOM rendered from the sources, the file tree alongside, and a numbered history as the design moves.
Using both
Write the story on Hackaday.io and link the board on BoardRepo from it. Readers get the narrative where it belongs and the design where it can be opened, and when you revise the board the BoardRepo link stays the same while the version behind it changes. The license you set on the project is shown on the board page next to the downloads.
Upload a project to get a link worth putting in a build log, or see the other comparisons.