On Oct 20, NVIDIA's GEAR lab (Jim Fan's team) open-sourced Flora, a model suite that turns human and robot manipulation video into timestamped action captions, process rewards, outcome rewards and rubric scores. It includes Flora-Captioner 27B and Flora-Rewarder 27B (both on Qwen3.5-27B) and Flora-TempSeg 9B (a LoRA on Qwen3.5-9B), with weights on Hugging Face under an NVIDIA non-commercial license. NVIDIA says it is the in-house data engine used to train GR00T, labeling 200,000 hours of video a day on 512 GB300s, matching GPT-6 Astra on annotation quality at roughly 125x lower cost.
Key Takeaways
- ✓Three models: TempSeg 9B segments actions, Captioner 27B writes one instruction per segment, and Rewarder 27B outputs dense process rewards and an episode success score
- ✓Cost (NVIDIA estimate): about $0.72 per hour of source video on eight GB300s at $10 per GPU-hour, versus about $88.49 for GPT-6 Astra at maximum effort, a 122-125x gap
- ✓Quality (NVIDIA 50-episode internal eval): 57.1% for Flora versus 53.7% for GPT-6 Astra; failure recall on DenseRewardBench is 53.3% while frontier API models mostly score under 1%
- ✓Scale: NVIDIA says Flora labels 200,000 hours of video a day on 512 GB300s to train GR00T-2
- ✓License: NVIDIA OneWay Noncommercial, research only, with commercial and production use explicitly unsupported

Key Decision Metrics at a Glance
Turn your technical choice into a development budget
Compare 40 dev plans & simulate token costs vs $20/mo subscriptions
Project Links & Resources
Direct AccessIn-Depth Technical Analysis
Background and the problem
Robot foundation models need huge amounts of labeled data: timestamped action captions to filter and balance pretraining data, dense process rewards for RL post-training, and outcome rewards to monitor real deployments. Those labels have mostly come from humans or expensive frontier multimodal APIs, which does not scale to hundreds of thousands of hours of video. NVIDIA's GEAR lab is now releasing Flora, the data engine it uses to train GR00T, aimed squarely at that bottleneck.
Architecture and how it works
Flora is a three-stage pipeline. Flora-TempSeg 9B, a LoRA adapter on Qwen3.5-9B, localizes operations window by window and stitches them into episode-level events. Flora-Captioner 27B, built on Qwen3.5-27B with SFT followed by RL, writes one English action instruction per segment using surrounding context. Flora-Rewarder 27B outputs an episode success score, short-step action-quality scores and failure reasons. It handles both human egocentric and robot video, and NVIDIA says it labels 200,000 hours of video a day on 512 GB300s.
Benchmarks
All figures are NVIDIA's: on a 50-episode internal eval, Flora scores 57.1% quality versus 53.7% for GPT-6 Astra at maximum effort. On DenseCaptionBench's human subset, segmentation [email protected] is 54.6 versus 44.2 for Astra, though Astra leads on the robot subset at 71.9 versus 66.9. RoboReward MAE is 40.0 (lower is better) versus 55.4, and DenseRewardBench failure recall is 53.3% versus 0 for Astra. At $10 per GPU-hour on eight GB300s, Flora costs about $0.72 per hour of source video against about $88.49 for Astra, roughly 125x; throughput figures are modeled, not measured.
Getting started
All three weights are in the nvidia/flora collection on Hugging Face and run with transformers (TempSeg loads as a PEFT LoRA); NVIDIA asks users to keep the FP32 Gated DeltaNet parameters alongside BF16 base weights. They suit research on robot data cleaning, sub-task segmentation, RL reward signals and deployment monitoring. The license is NVIDIA OneWay Noncommercial, research only, and NVIDIA stresses the outputs are annotations, not robot control or a sole safety monitor. The paper PDF and full comparison tables are on the project page.
Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.
Discussion & Comments
0Sign in to join the discussion
Connect with AI developers to exchange benchmark insights.