Skip to main content
CUPEL
CUPEL
FIND YOUR WAY
Request a pilot

Find the footage worth training on.

Trust

Your data stays in your bucket.

Refine runs locally or in an AWS workspace. Checkpoint intake stores a reference to the model. Customer self-serve onboarding and publication of contract-approved anonymised aggregates are planned.

Neutrality

One test, the same for everyone.

  • We sell no footage and no models. Cupel has nothing to gain from any vendor's data or any lab's policy scoring well.
  • No controlling stake is held by a robot lab, a data vendor or a model company.
  • Vendors can't buy a better score. Buyers pay for audits. Vendors pay only a flat, published fee to be listed.
  • No data moves between customers. No code path sells, exports or shares one customer's footage, checkpoints, world models or fleet data with another.
Where data lives

What stays, and what leaves.

Your cloud account

  • Raw and blurred footage
  • Refined sets, labels and exports
  • Checkpoints
  • World models fitted to your robots
  • Fleet recordings and episodes
Aggregates only

Cupel's shared ledger

  • Aggregated scores with score versions
  • Pooled A/B success counts and paired trial counts
  • Aggregated prediction accuracy
  • Fleet summaries

Aggregates reach the ledger only under the outcome-sharing clause in your contract. It gives Cupel the right to anonymised scores and outcomes, never the underlying data. Contracts with the clause cost less. Each customer's footage sits in a bucket of its own. Upload and download happen in the dashboard, so customers need no AWS account. A customer can connect a bucket in their own account instead.

Workspace admins can download pooled Refine Gate A outcomes for private review when the contract permits it. Publication is a separate release. Export workflows for the other categories are planned.

Licensing

Every model and dataset, on the record.

We record the licence of every model and dataset before it enters the pipeline. We don't use EgoDex (non-commercial) or Ego4D (commercial use unclear), or any hand model that depends on MANO.

Model or datasetUsed forLicence
V-JEPA 2 ViT-LEmbedding and scoringMIT (model card, checked Nov 2026)
Qwen3-VL-2B-InstructCaptions, run on our own GPUsApache 2.0
MediaPipeHands, hand pose, screen detectionApache 2.0
YuNetFace detection for blurringMIT
Build AI Egocentric-100KOpen footage for the first proofApache 2.0
CaptainCook4DOpen kitchen footage for testing the quality filterApache 2.0
Deploy safety

On-device safety and rollout rules

  • On-device watchdog. The development runtime holds or stops on late actions or a lost link. This behaviour has been exercised with a simulated driver. Physical verification is planned.
  • Test records and overrides. The development control plane requires a Test record by default and records overrides in the audit log.