Tell us what to capture
Collect the real-world human actions, spaces, tools, and failure cases robots need to learn.
→Robotics companies tell us what their robots need to learn. AuraOne finds the right people, captures the right tasks, checks the data, and delivers it for training.
Open vision-language-action model handoff when the program supports it.
Every session reviewed before it becomes training data.
HDF5, BVH, and JSON also ship with checksums and signed manifests.
This is the capture side. Real operators recording the real tasks your robot has to learn — on Aura Capture, reviewed and signed. We make the data. You train on it.
Tell us what your robot needs to learn. We capture it. You train on it.
Collect the real-world human actions, spaces, tools, and failure cases robots need to learn.
→Operators record the real-world tasks on Aura Capture — the spaces, tools, and failure cases your robot has to learn. Every session is reviewed and safety-checked before it counts.
→Training-ready dataset out. Raw files, task data, reviewer decisions, signed manifests, and checksums ship together.
Vetted operators record the real-world tasks your robot needs — on their phone, with depth, rigs, or teleop when the program calls for it. They get reviewed, and they get paid for accepted clips. The capture plan stays tied to the skill you asked for.
Robotics teams define the skill. AuraOne turns it into task briefs, finds the right people and places, checks each session, and packages the accepted data for training.
Every task maps to the people and environments it needs. Homes, kitchens, warehouses, factories, expert skill holders.
→Phones, cameras, depth, rigs, or teleop when the program requires it. The capture plan stays tied to the robot skill.
→Every session is reviewed before it becomes training data. Accept, rework, or reject — with the reason attached.
→Raw files, task data, reviewer decisions, accepted clip list, signed manifests, and checksums travel together.
The kinds of demonstration data robotics teams need before a policy can be trusted in the real world.
The environments where the real tasks happen — not a studio reconstruction, not a synthetic floor.
Task briefs tell operators what to record, what environment is needed, what tools or objects matter, how to frame the session, and what causes rework. The brief travels with the clip.
Pick up a bath towel, fold it in thirds, then stack it neatly.
Open the dishwasher, place plates and cups, adjust one item, close the rack.
Select irregular items, rotate them, and place them into a tote.
Handle an object, let it slip safely, pause, recover it, and reset the task.
Operators record real tasks, get reviewed, and get paid for accepted clips. Tiers move from a phone in a home kitchen all the way to teleop sessions in a robotics cell — gated by program scope and provider setup.
Home chores, simple object handling, phone capture.
Kitchens, warehouses, retail, hotels, facilities.
Tools, lab workflows, medical/surgical equipment, industrial tasks.
Remote operation and robotics control sessions.
Robot setup, environment walkthroughs, deployment support.
“The dataset showed up with the reviewer’s notes still attached to the rejected clips. That’s the part we’d been missing for years.”
We'll map the workflow. Pick the starting model. Standardize the session. Hand you the result.
OpenVLA
Reviewed robotics data, task context, accepted clip lists, manifests, and supported export packages.