← Robotics board · written 2026-10-14 by claude-opus-5-5 from the pipeline's evidence only

Maker's Pet (OOMWOO): Robotics · Skoor 80 (n=6, confidence 1.0)

What they built

Maker's Pet describes itself as "Home robots for makers." [source] Its product repo, OOMWOO, is an open-source robot vacuum you build yourself, using Raspberry Pi, 3D printing, Home Assistant, Arduino and ROS2. [source] It uses a 2D LiDAR to map and navigate, and it runs locally with no cloud required for regular functionality. [source] The license is Apache-2.0. [source] The README says it is "Not buildable yet." It runs in simulation today, and build instructions will follow once the first bill of materials is validated on real hardware. [source]

Record

Measured signals (n=6):
  • 11,577 stars and 734 forks on oomwoo, which was created 2026-06-10. [source]
  • 2,793 stars per month since creation. [source]
  • 177 commits in 90 days across 1 robotics repo. [source]
  • 9 distinct committers in 90 days. [source]
  • GitHub org created 2026-07-08, with 35 public repos. The org is unverified and lists its location as the United States. [source]
  • Website: makerspet.com. [source]

    • Founders, funding, revenue, customers and hiring are not in the evidence.

    Inference: The repo predates the org by about a month, so it was likely moved from a personal account. The stars measure attention. They do not measure a working product, because no hardware build exists yet.

    Why now

    The README cites an affordable 2D LiDAR, Raspberry Pi CM4/CM5 and ROS2/Nav2 as the stack. [source] It lists Home Assistant integration and local operation with no vendor lock-in as goals. [source]

    Inference: Demand appears to come from users who want a local, hackable alternative to cloud-tied vacuums. The evidence does not show the size of that market.

    Unknowns

  • Who founded the company, and what their technical background is: not in the evidence.
  • How many of the 9 committers are staff and how many are outside volunteers: not in the evidence.
  • The business model. The README lists optional cloud features and a stretch-goal app store. [source] Pricing and kit sales are not in the evidence.
  • The hardware timeline and bill-of-materials cost: not in the evidence.

    • Questions for the room

  • The README says the bill of materials is not yet validated on real hardware. What date is set for the first physical build, and what does it cost in parts?
  • Of the 9 committers in 90 days, who is on the team and who wrote the navigation stack?
  • With an Apache-2.0 license and 11,577 stars, what do you sell? How many stargazers have joined Discord or the newsletter, or asked to buy a kit?

    • What would move the Skoor

    These would raise it: a validated hardware build, named technical founders behind the core commits, and evidence that users will pay. These would lower it: a team that is mostly volunteers, a stall in commits, or no path to revenue from an open design.