Physical Intelligence · Bring Your Own Rig

Your rig, your format, your secrets. Our people and our rooms.

Robotics teams with a proprietary capture system, a custom helmet, a new gripper or a robot of their own get the whole bench — recruiting, environments, trained operators, SOPs and QC — without handing over the stack.

What it is

What gets captured, and why it is worth having.

Environment
Warehouse aisle, mixed light
Captured with
Customer's three-camera helmet rig, belt battery pack
Task
Shelve boxes from a pallet
Warehouse aisle, mixed light · Customer's three-camera helmet rig, belt battery pack

You ship us the hardware, or we build the rig to your drawings. We write the SOP with your engineers, train and test a crew on it, source or recreate the rooms, and run capture to your format and your naming. Your firmware, your file layout and your task taxonomy stay yours; nothing is retained after delivery.

Programs run under NDA with limited-visibility workflows: the crew sees the task, not the customer; the rig lives in a locked case between sessions; footage is pinned to your region from the first upload.

What it trains
  • Whatever your stack is built for
  • Embodiment-matched data on your own robot
  • Sensor combinations no off-the-shelf rig offers
  • Confidential programs ahead of a launch
The spec

How it is captured, and what you receive.

How it is captured
Your rig
Shipped to us, or built to your drawings
Your robot
Driven by our trained operators
Our rigs
Mixed in where you want a baseline
Custody
Locked cases between sessions, serials logged
Crew
NDA'd, limited-visibility, trained and tested on your SOP
Storage
Region-pinned from the first upload
What you receive
Format
Yours — container, layout, naming and metadata schema as specified
Streams
As many as the rig records; we sync and check what we can read
SOP
Written with your engineers, versioned, crew tested on it
Environments
Any class in the taxonomy, or your site, or a recreated space
Confidentiality
NDA, limited-visibility crews, no clip leaves your region
Episode
Set by your protocol
Environments and tasks

Where it is recorded, and what people are asked to do.

Tasks are recorded where they actually happen — not in a studio dressed to look like a kitchen. Hover a room to see the kind of setting the protocol calls for.

Kitchens

Indian, European and Brazilian home kitchens, lived-in and cluttered, plus small commercial kitchens and pantries.

Cooking preparationWashing upCupboards and drawersAppliancesPouring and scooping

Living rooms and bedrooms

Real Western homes in Spain, Germany, France and Italy, and apartments in India, Brazil, Japan and Korea. Sofas, wardrobes, shelves, laundry.

Tidying and foldingMaking bedsShelving and storageLaundryFurniture interaction

Offices

Open-plan and small offices: desks, pantries, meeting rooms, filing and cable clutter.

Desk tasksDocument handlingCables and peripheralsPantry tasksDrawers and storage

Retail and small shops

Kirana stores, groceries, pharmacies and supermarket aisles, with real stock and real customers out of focus.

Shelf restockingPicking to a listBagging and countersInventory checksCrates and boxes

Warehouses and light industrial

Racking aisles, packing benches, courier depots and small production lines with pallets, trolleys and parts bins.

Pallet to shelfParcel sortingPacking and tapingParts movementInspection

Workshops and labs

Mechanical and electronics workshops, repair benches and robotics labs where a follower rig can be set up.

Tool handlingAssembly and fasteningPegboards and racksBench tidyingTeleoperation setups

Agriculture and outdoor

Polytunnels, packing sheds, market stalls and yards, in daylight that changes from one episode to the next.

Sorting produceCrates and traysPruning and pickingWeighing and baggingLoading

Client-defined and confidential

Your site, or a space recreated to your drawings, run by an NDA'd crew with limited-visibility workflows and no clip leaving your region.

Proprietary workflowsRecreated spacesStealth programsOn-site with your rigYour robot, our operators
What ships

Deliverables, and the labels you can add.

Deliverables
  • Capture in your format and layout
  • Crew training records and SOP versions
  • Task and environment metadata per episode
  • QC status and reviewer chain per episode
  • Consent reference on every file
  • Quality report per batch: accepted, rejected, and why
  • Weekly drops to your bucket, region pinned at kickoff
Annotation add-ons
  • Annotation to your schema on Foundry
  • Parallel capture with our rigs for comparison
  • Rig maintenance and calibration logs
  • On-site supervision at your facility

Labelled on the same bench as our speech work, to a written guide, behind the same calibration test.

How a pilot runs

Ten to thirty episodes, then the volume.

  1. 01day 0
    Brief

    The task family, the environments, the rig, the sensors, the episode count. One page, agreed before anything is bought or anyone is recruited.

  2. 02week 1
    SOP and kit

    A written capture protocol — framing, lighting, where a task starts and ends, what counts as a failed take — and the kit list. Operators are trained and tested on it before a single episode is paid for.

  3. 03week 2
    Pilot episodes

    A small batch, ten to thirty episodes, delivered with QC status and a quality report. This is where the protocol breaks — on purpose, and cheaply.

  4. 04ongoing
    Review and scale

    You review the pilot, we fix the protocol, then the run scales on a weekly delivery cadence with the same report attached to every batch.

Turnaround
48 hrs
Written spec and quote
5 days
Sample episode in your format
2 weeks
Pilot batch with its QA report
Weekly
Delivery cadence once the pilot clears
Before an episode counts

What QC checks, every time.

  • Framing

    The task stays in frame; hands and workspace inside the protocol's bounds for the whole episode.

  • Exposure and focus

    No blown highlights or focus hunting beyond the tolerance set for the room.

  • Motion

    No camera whip, no dropped frames; IMU continuous where the rig has one.

  • Sync

    Every stream aligned within one frame; timestamps monotonic across cameras, state and action logs.

  • Task compliance

    Start and end states match the SOP; no skipped or reordered steps unless the protocol allows it.

  • Duration

    Inside the episode window for the task family; overruns are trimmed to the protocol, not the clip.

  • Metadata

    Environment, task, rig, operator id, session and consent reference present and valid on every episode.

  • Privacy

    No bystander faces, screens or documents without consent; blurred where the protocol flags it.

  • Calibration

    Intrinsics and extrinsics on file per rig and session for depth, stereo and multi-camera capture.

  • Labels

    Where annotation is ordered, agreement against the gold set above the threshold before the batch ships.