Partnership and Prototyping

Keero Bot is documented as a real hardware project rather than a loose concept. This page explains how the project is shared publicly, how prototyping fits into the workflow, and why some hardware details are intentionally not posted in full.

Prototyping Approach

Keero is being built in the open enough for people to understand the platform, but not as a full public manufacturing drop.

That means the public docs focus on:

• what the board is trying to do
• how the system is organized
• which modules and workflows are planned
• what firmware already exists
• what remains early or unfinished

Why The Docs Are Selective

The project follows a simple boundary:

• firmware and architecture can be discussed openly
• the hardware can be shown at subsystem level
• production-grade release files are not posted publicly

That keeps the project understandable without turning the docs into a straightforward copy package.

What Public Readers Can Learn Here

Even without full production files, someone reading the site can still understand:

• what the mainboard is responsible for
• how dock and tracks fit into the broader direction
• what the firmware roadmap looks like
• where the project is already concrete
• which parts are still prototype-stage

What Stays Private

To protect the project and keep the release balanced, some material is not published openly:

• fabrication packages
• full assembly outputs
• editable hardware source exports
• unrestricted production BOM data
• exact production-ready implementation details

That boundary is intentional. It keeps the hardware understandable, but not trivially clonable.

Working With Fabrication Partners

Prototyping partners such as PCBWay are still relevant to a project like this because small hardware projects depend on reliable fabrication, iteration, and assembly support.

If Keero moves into deeper manufacturing collaboration, the most useful conversations are usually about:

• prototype quality
• iteration speed
• assembly readiness
• bring-up support
• future module expansion

That is a much better fit for Keero today than pretending the project is already a finished commercial product.