Config closed-loop versus Lightwheel simulation

This split shows two different ways to get paid in robotics. Config is trying to own the moment where a customer says, make this robot do this task on my actual hardware, because it collects demonstrations, converts them into robot specific trajectories, fine tunes a policy, and feeds deployment failures back into training. Lightwheel sits earlier in the workflow, where teams build digital scenes, generate extra training examples, and test policies before touching the robot.1 2

• Config is more vertically integrated. Its Loop workflow covers collection, conversion, model training, live inference, and feedback from real rollouts, and it supports both its own CFG-1 model and outside models like GR00T N1.6 and Pi 0.5. That makes it closer to a deployment partner than a pure data vendor.1
• Lightwheel is strongest where simulation quality matters most. Its SimReady assets include measured physical properties like friction and deformation, EgoSuite captures first person demonstrations across 500 plus environments in 7 countries, and RoboFinals runs policy evaluation across multiple physics engines inside the NVIDIA Isaac ecosystem.2
• Maniformer helps show the market structure. It offers datasets, capture hardware, and some simulation assets, but stops short of Config's closed deployment loop and lacks Lightwheel's deep NVIDIA tied evaluation stack. In practice, buyers are choosing between raw data, self serve tooling, or a supplier that delivers a working task policy.1 2 3

The category is likely to separate into infrastructure sellers and outcome sellers. If robot buyers keep wanting faster time to a working task on real hardware, Config's closed loop becomes more valuable. If simulation proves it can cut deployment time and failure rates at scale, Lightwheel's sim first stack can become the default front end for robot training.1 2