2026-10-25 · 12 min read · 2,220 words
Microduck and Isaac Lab: the buyers guide to desk scale sim to real robotics
How educators and developers buy Microduck for NVIDIA Isaac Lab workflows, what to bundle, project ideas, and direct purchase links.
Buy Microduck for Isaac Lab: a desk scale path into sim to real
Reinforcement learning for locomotion used to mean a lab you could not enter without a grant. Microduck compresses the story onto a desk: train in NVIDIA Isaac Sim and Isaac Lab, refine against an Omniverse digital twin, transfer to fifteen real motors. Students see reward design, failure, and domain transfer in an afternoon instead of a semester of slides. This article is for teachers, students, indie researchers and curious engineers who want to buy the platform and start training. It ends with buy links for the robot and the Developer Expansion Kit.
Buy the Developer Expansion Kit
Sim to real gaps are not failures of the student. They are the subject. Carpet pile, table edges and cable snags will humble policies that looked perfect in simulation. Microduck is sized so those lessons are affordable and repeatable. Faculty should assign versioned policy checkins the way they assign code repos. Treat the robot as shared infrastructure with a short checkout log. That habit prevents the mystery of who flashed what before a demo day. If your institution blocks random USB devices, talk to IT before the robot arrives. Plan for a known network profile if any update path needs connectivity. Most locomotion policies run on device once loaded, which helps air gapped teaching scenarios.
What the training stack looks like when you own one
Cloud scale systems propose and score movement policies. Isaac Sim runs thousands of virtual Microducks that fall without breaking anything expensive. Policies that survive graduate to a joint accurate Omniverse twin where motor limits and sensor noise stop being theoretical. Only then does a policy land on hardware. As an owner you receive example policy repositories in the spirit of the factory skills: walking, sitting, recovery, and with the wheel kit, skating. Your first project should start from something that already walks. Blank file heroics are how beginners quit.
Buy the Developer Expansion Kit
Faculty should assign versioned policy checkins the way they assign code repos. Treat the robot as shared infrastructure with a short checkout log. That habit prevents the mystery of who flashed what before a demo day. If your institution blocks random USB devices, talk to IT before the robot arrives. Plan for a known network profile if any update path needs connectivity. Most locomotion policies run on device once loaded, which helps air gapped teaching scenarios. Pair Microduck units with existing GPU machines you already use for training. The robot is the body. The heavy learning still loves a proper workstation. Buy bodies for the classroom and keep training compute centralized if budget is tight.
Why the Developer Expansion Kit belongs in the first order
The kit adds servos for experimental joints, exposed sensor headers, alternative beak grip attachments, and mounting hardware designed to be reversible. Experiments should end with a robot you can restore, not a robot you sacrificed. If you know you will train custom behaviours, buy the kit with the robot. Waiting often means a second shipment and a week of temptation to drill holes you should not drill. The kit assumes comfort with code and calibration. It is a workbench, not a toy upgrade.
Buy the Developer Expansion Kit
If your institution blocks random USB devices, talk to IT before the robot arrives. Plan for a known network profile if any update path needs connectivity. Most locomotion policies run on device once loaded, which helps air gapped teaching scenarios. Pair Microduck units with existing GPU machines you already use for training. The robot is the body. The heavy learning still loves a proper workstation. Buy bodies for the classroom and keep training compute centralized if budget is tight. Outreach talks land harder when a biped walks the aisle. Budget time for battery swaps and a spare. A dead robot mid talk teaches the wrong lesson about physical AI.
Classroom deployment patterns that work
One robot per small group beats one robot per student for budgets, and beats a single shared robot for waiting time. Rotate roles: reward designer, simulation operator, hardware wrangler, note taker. Require a short writeup when a policy fails on the real floor after succeeding in sim. That gap is the lesson. Buy Graphite for labs that need a serious look. Buy Cream or Sky for outreach days when younger students visit. Add Extra Battery packs so the last period still has power.
Pair Microduck units with existing GPU machines you already use for training. The robot is the body. The heavy learning still loves a proper workstation. Buy bodies for the classroom and keep training compute centralized if budget is tight. Outreach talks land harder when a biped walks the aisle. Budget time for battery swaps and a spare. A dead robot mid talk teaches the wrong lesson about physical AI. Assessment ideas: score students on how clearly they explain a failed transfer, not only on a successful gait. Industry needs people who can debug reality.
Safety and supervision without killing curiosity
Microduck invites approach. Approachable is not indestructible. Keep sessions on flat indoor surfaces. Ban staircase experiments. Supervise younger users. Explain that fall recovery is trained behaviour, not permission to throw the robot. The warranty covers manufacturing defects on motors, sensors and servos. Liquid and unauthorized structural mods do not. Teach care as part of the lab culture when you buy.
Outreach talks land harder when a biped walks the aisle. Budget time for battery swaps and a spare. A dead robot mid talk teaches the wrong lesson about physical AI. Assessment ideas: score students on how clearly they explain a failed transfer, not only on a successful gait. Industry needs people who can debug reality. Open example policies shorten time to first motion. Resist the urge to rewrite everything in week one. Extend, then replace.
Project ideas for the first month after you buy
Week one: reproduce walk and sit with example policies, measure fall recovery success on your flooring. Week two: change a reward weight and document what breaks. Week three: add the wheel kit and evaluate skating on tile versus wood. Week four: use the developer kit to prototype a beak task for light object fetch. Publish what you learn if your institution allows it. The ecosystem around Hugging Face and open examples grows when owners share.
Buy the Roller Skate Wheel Kit
Buy the Developer Expansion Kit
Assessment ideas: score students on how clearly they explain a failed transfer, not only on a successful gait. Industry needs people who can debug reality. Open example policies shorten time to first motion. Resist the urge to rewrite everything in week one. Extend, then replace. When grants ask for broader impacts, a public Microduck demo day with local schools is a concrete paragraph. Buy early enough to rehearse.
Budgeting: robot, kit, dock, battery
Minimum serious setup: Microduck at $399 plus Developer Expansion Kit. Recommended teaching setup: add Charging Dock and Extra Battery. Performance setup: add Roller Skate Wheel Kit and Carry Case for events. Write the bundle into the purchase request so finance sees one story: desk scale physical AI for coursework. Link this article and the product pages.
Buy the Developer Expansion Kit
Assessment ideas: score students on how clearly they explain a failed transfer, not only on a successful gait. Industry needs people who can debug reality. Open example policies shorten time to first motion. Resist the urge to rewrite everything in week one. Extend, then replace. When grants ask for broader impacts, a public Microduck demo day with local schools is a concrete paragraph. Buy early enough to rehearse.
From curiosity to placed order
You do not need another whitepaper. You need a robot on the floor. Choose a finish, add the Developer Expansion Kit, place the order, and schedule the first lab session for after delivery. Preorder timing targets Christmas for the current batch in North America and Europe. Cancel free before ship if plans change.
Buy the Developer Expansion Kit
Assessment ideas: score students on how clearly they explain a failed transfer, not only on a successful gait. Industry needs people who can debug reality. Open example policies shorten time to first motion. Resist the urge to rewrite everything in week one. Extend, then replace. When grants ask for broader impacts, a public Microduck demo day with local schools is a concrete paragraph. Buy early enough to rehearse. Owning a bipedal robot changes the texture of a room. People slow down when they enter. Conversations start without icebreakers. That social effect is difficult to put on a spec sheet and easy to feel after a week. When you buy Microduck you are buying motion, learning, and a small daily spectacle that happens to be grounded in serious simulation tooling from NVIDIA and an open minded collaboration between Pollen Robotics and Hugging Face. Support expectations should stay adult. Response times are measured in business hours, not magic. Escalations exist when something goes wrong. Warranty language is written for desks, floors, children, and the occasional fall that was definitely the floor's fault. Read the warranty and shipping pages once before you buy so surprise never meets policy for the first time on a bad day. Software updates deserve patience. A policy flash is not a phone wallpaper change. Give the robot time. Test on clear floors. Keep the original example policies available so you can roll back your own experiments. The platform mindset says the robot should get better while remaining itself. Community matters. When owners publish clips of skating, recovery and beak tasks, new buyers understand what $399 purchases. Your own clip after you buy becomes part of that chain. Tag finishes so people know Cream from Sky at a glance. If you are still reading, you are past casual curiosity. Open the shop. Choose a finish. Add what you need. Place the order. The current batch will not wait on perfect certainty.
Owning a bipedal robot changes the texture of a room. People slow down when they enter. Conversations start without icebreakers. That social effect is difficult to put on a spec sheet and easy to feel after a week. When you buy Microduck you are buying motion, learning, and a small daily spectacle that happens to be grounded in serious simulation tooling from NVIDIA and an open minded collaboration between Pollen Robotics and Hugging Face. Support expectations should stay adult. Response times are measured in business hours, not magic. Escalations exist when something goes wrong. Warranty language is written for desks, floors, children, and the occasional fall that was definitely the floor's fault. Read the warranty and shipping pages once before you buy so surprise never meets policy for the first time on a bad day. Software updates deserve patience. A policy flash is not a phone wallpaper change. Give the robot time. Test on clear floors. Keep the original example policies available so you can roll back your own experiments. The platform mindset says the robot should get better while remaining itself. Community matters. When owners publish clips of skating, recovery and beak tasks, new buyers understand what $399 purchases. Your own clip after you buy becomes part of that chain. Tag finishes so people know Cream from Sky at a glance. If you are still reading, you are past casual curiosity. Open the shop. Choose a finish. Add what you need. Place the order. The current batch will not wait on perfect certainty.
Owning a bipedal robot changes the texture of a room. People slow down when they enter. Conversations start without icebreakers. That social effect is difficult to put on a spec sheet and easy to feel after a week. When you buy Microduck you are buying motion, learning, and a small daily spectacle that happens to be grounded in serious simulation tooling from NVIDIA and an open minded collaboration between Pollen Robotics and Hugging Face. Support expectations should stay adult. Response times are measured in business hours, not magic. Escalations exist when something goes wrong. Warranty language is written for desks, floors, children, and the occasional fall that was definitely the floor's fault. Read the warranty and shipping pages once before you buy so surprise never meets policy for the first time on a bad day. Software updates deserve patience. A policy flash is not a phone wallpaper change. Give the robot time. Test on clear floors. Keep the original example policies available so you can roll back your own experiments. The platform mindset says the robot should get better while remaining itself. Community matters. When owners publish clips of skating, recovery and beak tasks, new buyers understand what $399 purchases. Your own clip after you buy becomes part of that chain. Tag finishes so people know Cream from Sky at a glance. If you are still reading, you are past casual curiosity. Open the shop. Choose a finish. Add what you need. Place the order. The current batch will not wait on perfect certainty.
Ready to buy Microduck?
Official preorders from $499. Cream, Graphite, Lavender and Sky. Place your order on microducks.org.