Technology
NVIDIA Opens Flora Models to Label Robot Video and Score Actions
NVIDIA's Flora models turn robot and human video into timestamped instructions and reward labels. The release targets noncommercial research, with important limits on cost comparisons and safety use.
NVIDIA has made Flora, a three-model system for labeling human and robot video, publicly available. The company says its internal data engine processes as much as 200,000 hours of video per day on 512 GB300 GPUs. The release addresses a practical bottleneck for humanoid learning: identifying what happened during a demonstration, when it happened and whether the attempted task succeeded.
The research paper is dated October 20, 2026; the three Hugging Face model cards list October 15 availability. This is a research-tool release, with conditions that matter as much as the throughput claim. The published models are restricted to noncommercial research and development. They generate annotations rather than robot commands, and NVIDIA explicitly excludes their use as a sole physical-system safety monitor. NVIDIA's project page describes the system; the model cards define its intended use.
Key Stats
3 models
Segmentation, captions and rewards
9B / 27B
Base-model parameter counts
200,000 h/day
NVIDIA-reported internal scale
512 GPUs
GB300s in the reported run
How Flora Turns Recordings Into Training Signals
A video archive is not automatically a useful training set. Consider a hypothetical two-handed packing task: one hand steadies a carton, the other places an object, and a later movement corrects a poor placement. Labeling the entire recording “pack the box” loses the sequence. Labeling every movement separately can lose the purpose. A learning system needs descriptions at an appropriate level, tied to the right moments.
Flora separates that work into temporal segmentation, action captioning and reward modeling. Temporal segmentation identifies the intervals occupied by meaningful operations. Captioning names the attempted operation. A reward model grades the result or the quality of execution. Keeping those outputs distinct prevents a common conceptual error: an instruction describing an attempted placement does not prove that placement succeeded.
For humanoid developers, the immediate relevance is manipulation data. A recording can inform how a future robot reaches or handles objects without establishing anything about walking, balance or safe collaboration with people. Improvements in the annotation layer need downstream testing before they become claims about a machine's capabilities.
Under the Hood: Three Models, Different Jobs
The Flora-TempSeg model card describes a segmenter built on Qwen3.5-9B using low-rank adaptation, a training method that updates a smaller set of added parameters. It predicts local interval boundaries and continuation flags. The surrounding pipeline joins compatible fragments into episode-level events. It does not generate the action descriptions itself.
| Specification | Flora-TempSeg | Flora-Captioner | Flora-Rewarder |
|---|---|---|---|
| Base model | Qwen3.5-9B | Qwen3.5-27B | Qwen3.5-27B |
| Main output | Intervals and continuation flags | One action instruction per target interval | Outcome, step-quality or rubric scores |
| Annotation role | Locate operations | Describe attempted operations | Evaluate execution |
| Published use boundary | Noncommercial R&D | Noncommercial R&D | Noncommercial R&D |
The 27-billion-parameter captioner receives a specified target interval plus available neighboring events. Those surrounding events clarify the local operation; they should not become extra actions in the output. The reference input can combine a main camera and two wrist cameras, preserving their roles and timing. Its maximum frame budget is 64 frames across the target and context blocks.
That input design matters when hands obscure objects or a transfer only becomes clear in the next view. It also makes synchronization an engineering requirement. Mixing different moments into one apparent multi-camera observation would give an annotator contradictory evidence. Teams comparing annotation systems should preserve the original video clock and inspect ambiguous examples, rather than assume a fluent caption is accurate.
The rewarder's model card defines an episode outcome scale from 1 to 5. Its dense mode instead grades half-second steps within a 16-second window as failure, suboptimal or normal, with explanations for problematic steps. User-supplied rubrics provide another scoring route. These are different kinds of supervision: an overall partial-success score cannot identify every bad movement, while a locally normal action does not establish completion of the whole task.
NVIDIA's Data Strategy and the Research Around It
NVIDIA says Flora has been used to train GR00T models; its model cards specifically identify GR00T-2. The company is releasing a component of its data tooling, rather than announcing a new humanoid body or customer installation. The distinction gives researchers a concrete artifact to evaluate without turning an internal-use statement into evidence of a commercial fleet.
Reward learning also has an established research ecosystem. Robometer, a collaboration spanning universities and industry researchers, combines frame-level progress supervision with comparisons between trajectories, meaning complete sequences of robot behavior. Its project describes a dataset exceeding one million trajectories across 21 robot embodiments, including suboptimal and failed attempts. That approach highlights why failures are valuable training material, rather than merely recordings to discard.
The RoboReward dataset likewise pairs videos and task descriptions with graded outcomes. These research resources supply alternatives to treating every demonstration as equally good. They also show why evaluation needs several views of quality: understanding the instruction, detecting progress and recognizing failure are related but distinct problems.
Flora's public benchmark table reflects that unevenness. On DenseCaptionBench's human-video subset, NVIDIA reports joint annotation F1 of 37.4 for Flora versus 29.7 for GPT-6 Astra. On the robot subset, the ordering reverses: 51.0 versus 57.9. F1 combines precision and recall; these values are annotation metrics, not percentages of robot tasks completed. The evaluated pipelines also differ in visual inputs and inference budgets. The comparison does not support a universal claim that one model is better at robotics.
What Lower Labeling Costs Could Mean for Humanoids
The paper's cost analysis estimates $0.72 per source-video hour for Flora's segmentation-and-captioning pipeline versus $88.49 for maximum-effort Astra on a fixed 50-episode comparison. It does not price the full reward-labeling suite. The approximately 125-fold headline is conditional: Flora assumes eight GB300 GPUs priced at $10 per GPU-hour. Appendix D says the production GPU-hour denominator is unverified and excludes storage and deployment overhead. The API figure includes known usage, with some requests unpriced. These are different accounting bases, not complete invoices.
On an internal failure-labeling test, the paper reports 53.3% failure-step recall, alongside false failure labels on about 11% of normal steps. That tradeoff matters. Missing failures can contaminate training data; flagging normal behavior can waste review time. Neither outcome is captured by throughput alone.
The economic opportunity is therefore conditional too. If annotation becomes cheaper, a lab could inspect a broader range of tasks, retain more unsuccessful attempts and repeat experiments with revised labels. But it would still need to collect useful footage, respect data rights, maintain camera calibration and establish that the resulting training mixture improves behavior. Cheap labels on poorly chosen recordings do not solve those problems.
For an industrial buyer, the useful question is the total cost of producing a validated policy, not simply the price of describing an hour of video. A hypothetical evaluation should include human correction, decoding and storage, downstream training and physical testing. It should also examine whether savings persist on the buyer's own objects, lighting and work procedures. This is an evaluation framework, not a result demonstrated by the release.
A useful audit would keep examples of disagreement, rather than review only high-confidence successes. For instance, a camera may show an object entering a container while concealing whether it was released. An annotation could describe the attempt correctly yet overstate completion. Reviewing those cases against additional views or a human assessment would help identify which errors are tolerable for dataset search and which would distort a reward signal. The appropriate threshold depends on the later experiment and its consequences.
Frequently Asked Questions
Does Flora control a humanoid robot?
No. The released models annotate recordings and produce evaluation signals. They do not directly generate robot control commands, and NVIDIA says they must not serve as the sole safety monitor for a physical system.
Can a company use the released models in production?
The current model cards restrict intended use to noncommercial research and development and identify the NVIDIA OneWay Noncommercial License. They explicitly exclude supported commercial or production use. Public availability should not be read as unrestricted commercial permission.
What does the 200,000-hours-per-day figure measure?
It is NVIDIA's reported internal video-labeling scale across 512 GB300 GPUs. It is not hours of autonomous robot work, a delivered customer fleet or a throughput guarantee for a smaller installation.
Why separate captions from rewards?
A caption identifies the operation being attempted, while a reward describes execution quality or the outcome. A failed attempt can still have a correct action description. Keeping those labels separate makes it possible to learn from both successful and unsuccessful demonstrations.
Image attribution: Coolcaesar / Wikimedia Commons, with perspective and crop edits by Jacek Halicki, CC BY-SA 4.0. Photograph dated August 4, 2018. Archival company context, not Flora equipment. The downloaded rendition is unchanged; responsive resizing or display crops and any resulting image adaptation remain under the same license.
What's Coming Next: Test the Labels Against Behavior
The next meaningful evidence would connect annotation choices to downstream robot performance under a disclosed protocol. Researchers can compare manually reviewed labels, general-purpose models and specialized tools on the same held-out recordings, then test policies trained from those alternatives. Reporting correction effort alongside task outcomes would reveal whether apparent data-engine savings survive contact with physical experimentation.
For now, Flora makes an important part of robot development more inspectable. Its strongest contribution is a concrete separation of when an action happens, what is attempted and how well it goes. Its limits are equally concrete: research licensing, imperfect recognition and cost estimates that depend on substantial infrastructure.
The Bottom Line: Flora gives humanoid researchers another way to turn video into learning signals; useful robot behavior still has to be demonstrated through physical tests.