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

Waddle Labs: LLMs that control robots (Skoor 75, n=7, confidence 1.0)

What they built

Waddle Labs describes itself as "LLMs that control robots." [source]

Its product repo, waddle-sdk, is a "Hardware-agnostic SDK for agent-driven robotics" written in Python. [source]

The README says the SDK loads a strict site manifest, opens robot and camera drivers, enforces an owner envelope, and records timestamped raw evidence. Core semantics live in a Rust core. [source]

The SDK enforces keep-outs and collision rules, and fails closed on missing or incompatible geometry. [source]

It connects to a hosted service over gRPC using a customer/project API key. [source]

Inference: The open SDK is the client for a hosted product. The hold, e-stop and fail-closed design points at physical deployments, not simulation only.

Record (measured, n=7)

  • 373 commits in 90 days across 1 robotics repo. [source]
  • YC Summer 2026, status Active, stage Early. [source]
  • Team of 2, San Francisco. [source]
  • Marked as hiring, but no roles appear in the evidence. [source]
  • GitHub org created June 2025, with 4 public repos. Only 1 is in the evidence. [source]
  • waddle-sdk was created 2026-07-14 and last pushed 2026-10-13. It has 7 stars and 1 fork. [source]
  • Website live. [source]

    • Inference: The repo is about three months old, so the 373 commits cover its whole life. They do not show a longer track record.

    Why now

    Market timing and demand data: not in the evidence.

    The org dates from June 2025. The SDK repo dates from July 2026. [source]

    Inference: Work on the current product began around the YC batch, about a year after the org was created.

    Unknowns

  • Founder names and backgrounds: not in the evidence.
  • Customers, pilots, revenue: not in the evidence. The README refers to customer API keys but names no one. [source]
  • Funding beyond YC: not in the evidence.
  • Supported robots and models, and how LLM outputs become actions: not in the evidence.
  • Contents of the other 3 public repos: not in the evidence.

    • Questions for the room

  • The README describes customer/project API keys. How many outside sites are connected to the hosted service today, and on what hardware?
  • The repo logged 373 commits in 90 days with a team of 2. Who wrote them, and how is the work split between the Rust core and the Python frontend?
  • The SDK is described as hardware-agnostic. How many driver adapters exist, and how long does porting a new arm take?

    • What would move the Skoor

  • Raise: named external sites running the hosted product, or founder records in robot control.
  • Lower: no deployments beyond the founders' own hardware, or commits dropping off after the batch.