MechaSeed One — in development

Prototype direction / 01

Meet MechaSeed One.

A modular small-biped robot for physical AI learning, experimentation, and developer workflows.

Built on an Open Duck Mini v2-style hardware foundation, with a compatibility layer targeting MicroDuck-style developer workflows.

Small bipedModular hardwareDeveloper first

MechaSeed One engineering visualization with a wide chamfered head, two round eyes, modular shell, exposed leg joints, and broad biped feet — Engineering directionVisualization · final design may change

Real hardware+Small biped+Open robotics+Simulation to real+Repairable by design

What MechaSeed is

A real robot platform,
not an abstract idea.

Most physical-AI robots are expensive, closed, or difficult to access. MechaSeed exists to make small-biped robotics more modular, understandable, and practical to experiment with.

Affordable

A smaller, more practical entry point for embodied-AI experiments.

Modular

Built around inspectable joints, replaceable modules, and real fasteners.

Open-minded

Developer workflows are designed to stay legible, adaptable, and learnable.

Physical AI

A compact platform for taking ideas from simulation into motion.

Meet the robot

Built as a real robot,
not just a concept.

MechaSeed One is being designed around a practical small-biped architecture: modular joints, developer-friendly electronics, and a hardware stack suitable for learning, experimentation, and iteration.

Current status: engineering direction under validation. The visual below is not a final production specification.

Exploded-view visualization of the same MechaSeed One robot, showing its recognizable head, electronics, battery, body shell, servos, legs, and feet — MS—01 / System anatomyIllustrative hardware architecture

01Head module
02Neck articulation
03Main compute board
04IMU + sensing
05Modular body shell
06Battery + power
07Servo-driven joints
08Biped leg structure

What it is designed to do

A platform for motion,
learning, and iteration.

Walk + balance

Develop and test compact-biped locomotion.

Head articulation

Explore expressive pitch, yaw, and roll control.

Developer API

Work through a concise Python-oriented control surface.

Simulation first

Shape behaviors in simulation before moving hardware.

Modular hardware

Inspect, repair, replace, and iterate on real modules.

Built to experiment

Use a platform designed for learning, not a sealed appliance.

Capabilities shown are engineering targets, not shipping specifications.

Compatibility, clearly explained

Hardware you can build on.
Workflows you understand.

MechaSeed pairs a practical Open Duck Mini v2-style small-biped hardware foundation with a compatibility layer targeting MicroDuck-style developer workflows.

What it targets

MicroDuck-style developer workflows
Python-based control flows
Simulation-first experimentation
ONNX / runtime deployment patterns

How it works

Open Duck Mini v2-style hardware base
MechaSeed runtime
Compatibility mapping layer
MicroDuck-style API surface

What it does not mean

Not official MicroDuck hardware
Not a direct clone
Not every upstream policy unchanged
Independently developed

Compatibility has a specific meaning here. It refers to developer workflows and API concepts, not identical hardware or guaranteed policy interchangeability.

Architecture / target stack

From practical hardware to a familiar developer surface.

Click a layer to see the role it plays. The compatibility layer is an adapter between MechaSeed’s runtime and familiar control concepts—it is not a claim of official equivalence.

01 / FoundationOpen Duck Mini v2-style hardware

A practical small-biped layout informs the mechanical and electronics foundation.

Compatibility matrix

Specific beats vague.

Current targets are shown plainly so expectations can evolve with evidence.

Layer	Status
Small-biped hardware foundation	Planned
Modular joint architecture	Planned
MicroDuck-style control concepts	Targeted
Developer-friendly API surface	Planned
Simulation-oriented workflow	Planned
Direct official policy compatibility	Not promised

Try the API

See how a command
becomes motion.

This illustrative interface shows the intended command model. The API is not yet a released contract.

# Walk forward and turn
robot.move(
  vx=0.2,
  vy=0.0,
  yaw=0.3,
)

# Aim the articulated head
robot.head(
  pitch=0.15,
  yaw=-0.2,
  roll=0.05,
)

# Read joints and sensing
state = robot.state()

print(state.imu)
print(state.joints)

Command→Compatibility layer→Runtime→Robot

MechaSeed One engineering visualization used to show which hardware area a sample command affects

MOVE / LOCOMOTIONLeg joints + balance control

Built for developers, students, and labs

From first motion
to serious experiments.

A desktop robot should be close enough to inspect, practical enough to iterate on, and open enough to teach with.

A developer testing a compact biped robot beside a laptop running code and simulation software — 01 / Field note

Developers + makers

Give your code a body.

Prototype commands, inspect state, and connect software to motion without inventing a complete hardware stack first.

Two university students studying a modular biped robot in a bright robotics lab — 02 / Field note

Students + educators

Make robotics legible.

Learn with visible mechanics, approachable software concepts, and hardware intended to be understood and repaired.

A small biped robot performing a gait test on a laboratory workbench — 03 / Field note

Labs + teams

Test at desktop scale.

Explore locomotion, articulation, sensing, and repeatable physical-AI experiments on a compact platform.

Questions, answered plainly

Before you join.

Still curious? Talk to a human.

What is MechaSeed One?

MechaSeed One is a planned modular small-biped robot for physical-AI learning, experimentation, and developer workflows. It is currently in prototype validation; the images on this page show the intended engineering direction, not final production hardware.

Is MechaSeed a clone of MicroDuck?

No. MechaSeed is an independently developed platform. It aims to support familiar MicroDuck-style developer workflows through a compatibility layer, rather than reproduce official MicroDuck hardware.

What does compatibility mean?

Compatibility refers to developer workflows, API concepts, and simulation-oriented control patterns. It does not mean identical hardware or guaranteed policy interchangeability.

Is it official MicroDuck hardware?

No. MechaSeed is not affiliated with or endorsed by MicroDuck or Pollen Robotics.

Will every upstream policy run unchanged?

That is not promised. Differences in geometry, actuators, sensing, runtime behavior, and calibration may require adaptation and validation on MechaSeed hardware.

Who is it for?

Makers, robot developers, students, educators, university labs, and small robotics teams that want a practical route into small-biped physical-AI experiments.

Is pricing finalized?

No. Pricing and final specifications are still under evaluation. The founding waitlist helps us understand the configurations and price ranges that matter most.

When will it be available?

There is no announced launch date. The next milestone is a working engineering prototype, followed by a small founding batch only after the core behavior is validated.

Help shape the first build

Build the evidence
with us.

Join for honest prototype progress, compatibility updates, early access, and founding-batch news.