Skip to content
Operant

FAQ

Frequently asked questions

Answers about custom capture programs, ownership, timelines, and discovery calls.

Getting started

Open datasets rarely match your robot, sensors, or deployment environment. Operant designs capture around your evaluation goals, not a fixed catalog download.

Pilots often run 2–4 weeks. Production scales over months depending on diversity targets and geographies.

We review your stack, behaviors, sensors, volume, and quality bar, then outline a pilot and commercial framework.

Robotics and physical AI teams with defined milestones who need auditable real-world data, not generic bulk downloads.

Target behaviors, sensor list, a staging environment, and an engineering point of contact for format validation.

No. Operant runs custom capture programs for your environments and robots, we are not a broker or off-the-shelf catalog.

Yes. Engagements grant your organization ownership of captured data with terms documented during scoping.

We follow your policies and applicable regulations with consent workflows and secure transfer agreed before capture.

NDAs and restricted-access delivery are standard for commercial robotics programs.

Technical

RGB-D, LiDAR, IMU, force/torque, and proprioceptive streams are common. We finalize the sensor list on your discovery call.

Time-synchronized logs, calibration files, metadata, and optional labels in formats your training pipeline expects.

Yes, label schemas, QA, and tooling integrations can be included when defined in scope.

Automated sync checks, sample review gates, and acceptance tests tied to the statement of work before scale.

We deliver metadata and formats compatible with sim-to-real workflows and can align episode IDs with your sim domains.

Yes, failure taxonomy and sampling ratios are defined explicitly for eval-oriented programs.

Teleoperation and demonstration capture are core offerings with multi-camera synchronization.

Commercial

Custom projects are scoped fixed-fee or milestone-based after discovery, aligned to environments, sensors, and volume tiers.

Yes, retainer-style programs maintain diversity and refresh tail behaviors as your product evolves.

Pilots are designed to be meaningful but bounded; production scale follows proven pilot metrics.

Operations

We run programs in North America and Europe by default; other regions are available with lead time for permits and staffing.

We typically capture on client or lessor hardware; operator staffing and rigging are part of scope.

Scope your capture program

Book a discovery call to align on your stack and data requirements.

Book a discovery call