Robot Development
71 tools
Robot development platforms include middleware, simulation, motion planning, perception libraries, compute platforms and vendor SDKs. Verify operating system and architecture, ROS version, driver maintenance, licensing, hardware interfaces, real-time needs and documentation, then test real hardware for errors simulation cannot capture.
Reachy 2
Robot Development
Reachy 2 is a humanoid robot developed by Pollen Robotics for interactive and manipulation applications.
Foxglove Agents
Robot Development
Foxglove Agents let you work with your robot data in natural language, using a built-in agent or your own MCP client.
Buy or sign up directly
LeKiwi
Robot Development
LeKiwi is an open-source mobile robot platform from Hugging Face's LeRobot project for assembling, teleoperating, and training real-world robot policies.
Open source
SO-ARM101
Robot Development
SO-101 is Hugging Face LeRobot's flagship robot arm, documented with assembly, motor setup, and calibration instructions.
Open source
Robotnik RB-FIQUS
Robot Development
Heavy-load outdoor omnidirectional research platform
Not specified · Contact the vendor for pricing
Robotnik RB-KAIROS+
Robot Development
Omnidirectional mobile manipulator with UR arm options
Not specified · Contact the vendor for pricing
Robotnik RB-ROBOUT+
Robot Development
Heavy-load mobile manipulator with UR arm configurations
Not specified · Contact the vendor for pricing
Robotnik RB-VOGUI+
Robot Development
Outdoor mobile manipulator with configurable UR arms
Not specified · Contact the vendor for pricing
Robotnik RB-THERON+
Robot Development
Indoor mobile manipulator configured with a UR7e arm
Not specified · Contact the vendor for pricing
Robotnik RB-VOGUI
Robot Development
Omnidirectional outdoor base for robotics development
Not specified · Contact the vendor for pricing
Robotnik RB-SUMMIT
Robot Development
Indoor and outdoor mobile base for robotics experiments
Not specified · Contact the vendor for pricing
Clearpath Warthog
Robot Development
Large research UGV for outdoor payload integration
Not specified · Contact the vendor for pricing
Clearpath Ridgeback
Robot Development
Omnidirectional indoor base for mobile manipulation
Not specified · Contact the vendor for pricing
Clearpath Jackal
Robot Development
Compact field-research UGV with ROS 2
Not specified · Contact the vendor for pricing
Clearpath Husky A300
Robot Development
100 kg outdoor research base with ROS 2 Jazzy
Not specified · Contact the vendor for pricing
Husarion ROSbot XL
Robot Development
ROS 2-native indoor development robot
Not specified
Clearpath TurtleBot 4
Robot Development
ROS 2 learning robot with Standard and Lite variants
Not specified · Contact the vendor for pricing
ROBOTIS TurtleBot3 Waffle Pi
Robot Development
Compact ROS mobile platform for education
Not specified
ROBOTIS TurtleBot3 Burger
Robot Development
Compact ROS mobile platform for education
Not specified
AgileX LIMO PRO
Robot Development
Small ROS education robot with Orin Nano computing
Buy or sign up directly
Robotnik RB-SUMMIT+
Robot Development
Mobile research manipulator with Kinova arm options
Not specified · Contact the vendor for pricing
AgileX RANGER AIR
Robot Development
Omnidirectional mobile base for embodied-AI systems
Not specified
AgileX BUNKER PRO 2.0
Robot Development
Heavy-duty tracked research base
Not specified
AgileX BUNKER MINI 2.0
Robot Development
Compact tracked research platform
Not specified
FAQ
How to start robot development from zero?
Start with Python/C++, Linux and version control, then learn ROS 2 nodes, topics, services and transforms through a small simulated project. Before buying hardware, confirm driver, interface and maintenance status.
ROS or ROS 2?
Evaluate ROS 2 first for new work, but legacy systems may still use ROS 1. Decide from target hardware, existing code, driver support and team environment, and do not confuse a distribution with the middleware protocol version.
Can simulation replace real-robot testing?
Simulation is useful for interfaces, logic, planning and parts of perception, but sensor noise, latency, friction, compliance, mechanical tolerances and environmental variation still require hardware tests. No fixed substitution percentage fits every project.