Now recruiting capture teams worldwide. Get paid to record first-person video of real work.

Apply to capture

Task family

Egocentric Kitchen Deep Clean and Degreasing Data

Spray degreaser on hoods, walls and counters, scrub with pads and rinse; empty and scrub fryers, hoods, floors and shelving with degreaser, brushes and mops: a commercial kitchen deep clean is slow, wet, two-handed work, and the useful view of it is the cleaner’s own. This page covers egocentric kitchen degreasing data for the two Restaurant & Commercial Kitchen catalog rows that name this work, as first-person commercial kitchen deep clean video: what the head view and the wrist views keep in frame, which streams the site states, and what it does not state. We run custom restaurant cleaning data collection fast and on demand against a spec you write, as a scrub and degrease dataset, custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs.
Catalog rows
Two in Restaurant & Commercial Kitchen: a degrease-and-scrub row (Easy) and "Restaurant Kitchen Deep Clean" (Medium)
Status
One Active collection and one Ready to deploy, as the catalog lists them
Streams
Ten in the site’s wider stack, synced under 2 ms
License
Perpetual, buyer-owned

Requirements

What does kitchen deep clean capture need that a generic kitchen clip does not?

01

The pad, the surface and the hand in view together

Scrubbing is a hand, a pad or brush and a surface moving against each other. First-person capture keeps the hands and the work area in frame, and 3D hand pose carries a per-joint visibility flag, so a finger hidden behind a pad is flagged rather than guessed.

02

A spec that names the step and the surface

The site’s skill-spec guide says to name the verb and the noun rather than a broad activity. A spec for this family names the surface or appliance and the step, such as spraying a hood or emptying a fryer, and where one finished step starts and ends, so each can become its own labeled segment.

03

Wet and glossy surfaces handled on purpose

The site states that wet and reflective surfaces degrade active-stereo depth, and that kitchen captures ship per-frame depth confidence maps so you can mask rather than guess. A rinsed hood or a wet counter is exactly that case.

04

Steps on one clock

Emptying, spraying, scrubbing and rinsing are different steps in a chain. Streams are hardware-triggered onto one clock, and action segments carry start, end, verb and noun as the skill spec defines them.

Definition

What is egocentric kitchen deep clean and degreasing data?

It is first-person video of a person degreasing and deep cleaning a commercial kitchen, recorded from their own point of view with synchronized sensor streams alongside. The tasks are the two rows the site’s catalog lists in Restaurant & Commercial Kitchen: spraying degreaser on hoods, walls and counters, scrubbing with pads and rinsing, and emptying and scrubbing fryers, hoods, floors and shelving with degreaser, brushes and mops. The camera sits on the head, close to what a robot’s onboard camera would see over a hood or a work surface, so the frames show what the hands and the pad do rather than a distant view of someone cleaning.

People reach this topic through close cousins: egocentric kitchen degreasing data, a scrub and degrease dataset, first-person commercial kitchen deep clean video, or custom restaurant cleaning data collection. They describe one request from different angles, and the work is the same: write the task down, collect it on demand in real kitchens, and receive validated episodes. The data is human capture by paid, consented contributors, not robot or teleoperation data. Nothing on this page states that the video carries a cleanliness score, a grease-coverage map or a contact-force reading.

Catalog rows

Which catalog rows does this page rely on, and what is their status?

Two, both in Restaurant & Commercial Kitchen under Food & Beverage, in the catalog data file lib/commercial-catalog-data.ts. The catalog lists examples for the environment such as a sit-down restaurant kitchen, a café, a coffee shop, an artisan bakery and a patisserie. "Degrease and scrub kitchen surfaces using degreaser and scrub pads" is described as spraying degreaser on hoods, walls and counters, scrubbing with pads and rinsing the surfaces clean, is rated Easy and is listed as Active collection.

"Restaurant Kitchen Deep Clean" is described as emptying and scrubbing fryers, hoods, floors and shelving with degreaser, brushes and mops, is rated Medium and is listed as Ready to deploy. Both list a head-mounted phone or a multiview rig as the capture setup. The site says nothing further about what each status means in volume or hours, so this page claims none, and what applies to a given order is confirmed when you request the quote. This page names only the tools and surfaces that appear in the two rows. The first table below reproduces them as the catalog states them.

Nearby rows

Which nearby catalog row is context only?

"Trash & Recycling Removal in Kitchen" sits in the same environment. It is described as pulling full bags and recycling from the kitchen, carrying them to the bins and relining the cans, is rated Easy and is listed as Ready to deploy, with the same head-mounted phone or multiview rig capture setup. It is not a degreasing or deep clean row, so this page treats it as nearby context only and builds nothing on it.

The dishwashing and line setup rows in that environment are covered by their own pages, listed in the comparison table below. They are not part of this page’s scope.

Difference

How is this different from the stereo sibling, the food plant page, the wiping page and the line setup page?

The stereo kitchen deep clean and degreasing page covers the same two rows as stereo capture, agreed through the site’s general stereo offer and delivered as MCAP. This page covers them as egocentric capture as the catalog lists it, with the head and wrist views and the synchronized streams, and does not treat stereo or MCAP as the main topic. If your pipeline wants a calibrated stereo pair or an MCAP file, start from the stereo page.

The egocentric food plant sanitation and washdown page lists both kitchen rows beside two plant washdown rows, so it is a four-row page centred on sanitation. The egocentric wiping page covers wipe-and-reset rows. The egocentric kitchen line setup page covers the two pan and line rows. The stereo dishwashing page treats the two rows here as half of a four-row dish-pit set. This page narrows to the degreasing and deep clean rows alone and goes further into their surfaces, tools and failure modes. The second table below sets the pages side by side.

Why egocentric

Why capture kitchen deep clean and degreasing work from the cleaner’s point of view?

A deep clean is about where the hands, the tool and the surface sit relative to one another: how far a spray bottle is from a hood, where a pad has already been on a wall, how a brush reaches into a shelf. A head-mounted camera keeps the hands, the tool and the work area in one view, and it is the view a robot working the same kitchen would have. Two wrist cameras, where the spec asks for them, give a second and closer view of the hands than the head camera alone, which matters when a hand presses a pad flat or reaches under a hood.

The site gives no label for a degreased surface, a clean fryer or a finished shelf, and states no coverage measure for a scrubbed area, so what counts as finished is written into the spec up front. The catalog marks the degrease row Easy and the deep clean row Medium, which are skill ratings only, and the site states no task time for either.

Capture setup

What does the capture setup look like, and what is not stated?

The catalog states one capture setup for both rows: a head-mounted phone or a multiview rig. The site describes a wider stack that every program draws on: a head camera, two wrist cameras, depth, IMU, 3D hand and body pose, instance segmentation and action labels, ten streams in all, hardware-aligned to under 2 ms. Its hard-environments stack lists a global-shutter 4K/60 head camera with a 120° lens, two 1080p/60 wrist cameras, a depth sensor at 848×480 and 30 fps, and 200 Hz 6-DoF IMUs.

Which of those a kitchen deep clean order uses is set in the skill spec, and the third table below sets what is stated beside what is not. Every stream is hardware-triggered onto one clock, and the rig is calibrated at the start and the end of each session, with an episode accepted only if reprojection stays under 0.28 px RMS. The catalog states that a multiview rig adds synchronized third-person angles when the spec asks for them. The site does not state how capture hardware is protected from water or spray, and it does not state a camera count or resolution specific to these rows.

Stereo

Is this stereo capture?

Not on the rows. The catalog lists a head-mounted phone or a multiview rig, and the site does not state that a stereo pair is running on these rows. Stereo applies only through the site’s general stereo offer: a stereo pair is a capture choice agreed in the skill spec and confirmed on a Spec Pilot. The stereo kitchen deep clean and degreasing page describes that route, including what a calibrated pair adds and what the site does not state about it.

On depth in general, the site states that metric depth is recovered from a calibrated stereo rig rather than from a standalone depth sensor on the instrumented tier, and that depth confidence maps ship so low-confidence regions can be masked. This page does not state which tier a kitchen order uses.

Streams

Which streams and labels can a kitchen deep clean episode carry?

The site states an episode schema with hand pose of 21 joints per hand and a per-joint visibility flag, contact events, action segments with start, end, verb and noun, per-frame instance masks stored at 848×480, and one task instruction per episode. Calibration is measured every session and ships with the episode. Which of these a given kitchen order includes is set in the skill spec, and the site does not state a topic naming, an encoding or a rate for any of them on these rows.

Force and tactile readings are not among the listed streams, and no robot or teleoperation data is captured. The site states no degreased, clean or dry label, no grease-coverage map and no scrub-stroke label, so none is promised here. Delivery formats the site names are RLDS, LeRobot and WebDataset, with HDF5 and zarr as further options set in the spec.

Failure modes

What goes wrong when you record kitchen deep clean and degreasing from the cleaner’s view?

Hand occlusion is the first risk. Fingers go behind a scrub pad, a brush or a mop head, and a tool can hide the surface it is working. The visibility flag on each joint is the answer the site gives, contact events mark when a hand meets an item, and a spec can ask for wrist views so a grip the head camera loses is still recorded.

Wet and reflective surfaces are the second. Per-frame depth confidence maps ship for kitchen captures so low-confidence regions can be masked rather than trusted, and per-frame instance masks cover wet or reflective cookware, because masks propagated frame to frame do not track them well. Spray, steam, lighting and clutter around a hood or a fryer are not described on the site, so how they affect a capture is Not stated.

An episode is also rejected when the manipulated object is out of frame for more than 15 percent of it or an undocumented bystander appears, and a reject log ships with every batch. Capture at your own facility is listed as not offered.

Sequences

How should repetitive scrubbing sequences be segmented?

A deep clean chains steps that look alike on camera: spraying, scrubbing and rinsing a hood, then the same on a wall, then on a counter, or emptying a fryer and then scrubbing it. Action segments carry start, end, verb and noun, so the spec decides where one segment ends and the next begins, and which object is the noun.

The site states no episode length, no segment count and no scrub-stroke label for these rows. Whether an episode is one surface, one appliance or a whole station is set per program. Put that boundary and the verbs you expect into the skill spec, and check them on the Spec Pilot before you scale.

Privacy

How are people and items in frame handled?

For every delivered episode the site states that faces, plates and screens are blurred irreversibly, and that footage that cannot be de-identified is discarded. Who may be in frame, and how a kitchen’s own staff, menus or labels are handled, is agreed in the spec. The anonymization page has the full statement.

The site states no cleaning-standard, chemical, throughput, accuracy, food-safety or certification claim for these rows, so this page describes none. It also states no restaurant, client or brand name, no degreaser brand or dilution ratio, no equipment model, no surface count and no task time for these rows. Each of those is Not stated.

Scale

How do off-the-shelf data and custom collection combine for kitchen deep clean?

Off-the-shelf covers what is already in stock. This page does not claim an off-the-shelf dataset of kitchen deep clean or degreasing, so this is custom collection: custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs.

Where coverage is deep, the median time from signed spec to first validated batch is a median of 48 hours; where it is thin, turnaround runs three to four weeks. The site does not say which speed applies to a kitchen order, so ask when you request the quote. Collections are billed per validated hour.

Ordering

How do you order an egocentric kitchen deep clean and degreasing dataset?

Describe the surfaces and appliances and their order, the degreaser, pads, brushes and mops and their start state, what counts as a finished surface, and the variation your pipeline is missing. Then name the streams you want, whether wrist views are needed, how episodes are bounded, and the delivery format your loader expects.

Most programs begin with a Spec Pilot, a small first batch that proves the spec and accept criteria on real footage before you scale. The fourth table below shows what each spec element decides.

At a glance

What you get.

Catalog rows
"Degrease and scrub kitchen surfaces using degreaser and scrub pads" (Easy, Active collection) and "Restaurant Kitchen Deep Clean" (Medium, Ready to deploy), in the Restaurant & Commercial Kitchen environment of the Food & Beverage sector
Catalog descriptions
"Spray degreaser on hoods, walls and counters, scrub with pads and rinse the surfaces clean."; "Empty and scrub fryers, hoods, floors and shelving with degreaser, brushes and mops."
Environment examples
Sit-down restaurant kitchen, café, coffee shop, artisan bakery, patisserie
Catalog capture setup
Phone (head-mounted) / multiview rig, on both rows
Stereo
Not listed on the rows; available only through the general stereo offer, see the stereo sibling page
Hand pose
21 joints per hand with a per-joint visibility flag
Sync
Hardware-triggered onto one clock; under 2 ms across streams
License
Perpetual, irrevocable, buyer-owned, non-exclusive by default

Every collection runs through the same seven-stage end-to-end custom collection pipeline. End-to-end custom data collection is a managed service that takes an AI data need from problem to owned dataset in a single accountable pipeline.

Catalog rows

Which catalog rows cover kitchen deep clean and degreasing?

The two rows this page relies on, plus one nearby row shown as context only, with the catalog description, environment, skill, capture setup and status as listed.
Task (as listed)Description (as listed)EnvironmentSkillCapture setupStatus
Degrease and scrub kitchen surfaces using degreaser and scrub padsSpray degreaser on hoods, walls and counters, scrub with pads and rinse the surfaces clean.Restaurant & Commercial KitchenEasyPhone (head-mounted) / multiview rigActive collection
Restaurant Kitchen Deep CleanEmpty and scrub fryers, hoods, floors and shelving with degreaser, brushes and mops.Restaurant & Commercial KitchenMediumPhone (head-mounted) / multiview rigReady to deploy
Trash & Recycling Removal in Kitchen (nearby context only)Pull full bags and recycling from the kitchen, carry them to the bins and reline the cans.Restaurant & Commercial KitchenEasyPhone (head-mounted) / multiview rigReady to deploy

Compared pages

How does this page differ from the neighbouring kitchen cleaning pages?

Each page, which of the two deep clean and degreasing rows it covers, the row statuses it lists and how it treats capture. “Not covered” means the page leaves the rows out.
PageDegrease and deep clean rowsStatuses as liveCapture treatment
This page: egocentric kitchen deep clean and degreasing dataBoth rows, and only theseDegrease row Active collection; deep clean row Ready to deployEgocentric capture as the catalog lists it; stereo only through the general stereo offer
Stereo kitchen deep clean and degreasing dataBoth rows, and only theseDegrease row Active collection; deep clean row Ready to deployStereo through the general stereo offer, with MCAP delivery
Egocentric food plant sanitation and washdown dataBoth rows, with two plant rowsDegrease row Active collection; deep clean and both plant rows Ready to deployEgocentric catalog treatment, centred on sanitation
Stereo dishwashing and kitchen sanitation dataBoth rows, with two dishwashing rowsThree rows Active collection, one Ready to deployStereo and MCAP, centred on the dish pit
Stereo food plant sanitation washdown dataNot covered; two plant washdown rowsBoth plant rows Ready to deployStereo and MCAP, for plant rows
Egocentric wiping and surface cleaning dataNot covered; wipe and reset rowsRows listed there are mostly Available on request, with some Active collection and Ready to deployEgocentric treatment
Egocentric kitchen line setup and breakdown dataNot covered; two pan and line rowsOne Active collection, one Ready to deployEgocentric treatment, for line rows

Stated vs not stated

What the site states about egocentric capture for kitchen deep clean and degreasing

Left to right: the item, what the site states, and what that means for a kitchen order. “Not stated” means the site does not say.
ItemWhat the site statesFor a kitchen order
Catalog capture setupPhone (head-mounted) / multiview rig on both rowsStated; a stereo pair is a spec choice through the general stereo offer
Wider stackTen streams: head camera, two wrist cameras, depth, IMU, 3D hand and body pose, instance segmentation, action labels; aligned under 2 msWhich streams a kitchen order uses is set in the skill spec
Hard-environments stack4K/60 head camera, 120° lens; two 1080p/60 wrist cameras; depth 848×480 at 30 fps; 200 Hz 6-DoF IMUWhether a kitchen order uses it: Not stated
Wet and reflective surfacesDegrade active-stereo depth; kitchen captures ship per-frame depth confidence mapsBehaviour on a given hood or fryer is Not stated
Hands and objects21-joint hand pose with a per-joint visibility flag; contact events; per-frame instance masks at 848×480Stated
Calibration and syncMeasured every session and shipped with the episode; 0.28 px RMS gate; hardware-triggered onto one clockStated
Row statusOne row is Active collection and one is Ready to deployNo volume or hours are claimed on this page
Spray, steam, lighting and clutter effects, water protection for hardwareNot statedAgreed in the skill spec, or not claimed on this page
Degreased or clean labels, chemicals and degreaser brands, dilution ratios, equipment models, surface counts, task times, throughput, error rates, client names, food safety, certification, force data or resultsNot stated; the rows say degreaser, scrub pads, brushes, mops, hoods, walls, counters, fryers, floors and shelving onlyAgreed in the skill spec, or not claimed on this page

Skill spec

What the skill spec fixes for an egocentric kitchen deep clean and degreasing order

Spec element and where a buyer can see it in the delivery. “Set per program” means the site states no fixed value.
Spec elementWhat it decidesWhere it shows up
Surfaces, appliances and orderWhat one step is: empty, spray, scrub, rinse, and which hood, wall, counter, fryer, floor or shelf comes nextEpisode boundaries and action segments; set per program
Which rowsDegreasing, deep clean, or bothSet per program; the degrease row is Easy, the deep clean row is Medium
Tools and start stateWhich degreaser, pads, brushes and mops, and how the surfaces beginSet per program; the site states no clean or degreased label
Episode boundaryOne surface, one appliance, one station or a full chainSet per program; the site does not state an episode length
Rig and streamsHead camera, wrist views, hand pose, IMU and any othersThe streams you can read; confirm on the Spec Pilot
Delivery formatHow the data is packagedRLDS, LeRobot or WebDataset, with HDF5 or zarr as options
Accept criteriaWhat passes QAReject log per batch
PrivacyHow people and items in frame are protectedFaces, plates and screens blurred at ingest
LicenseWho owns the datasetPerpetual, irrevocable, buyer-owned, non-exclusive by default

Example footage

What does egocentric kitchen footage look like?

Two real clips already published on this site. The first is a home-kitchen clip of an operator browning mince at a gas range, listed in the site’s Kitchen & food prep set. The second is a format and rig example: a head-mounted stereo capture with hands in frame. Neither shows degreasing, scrubbing or a kitchen deep clean.

sample-dinner-cooking.mp4 · Kitchen & food prep · home kitchen, stirring in a skillet · 640 × 360 web preview · not a cleaning clip
egocentric_stereo_sample.mp4 · head-mounted stereo · hands in frame · 1920 × 1080 web preview · rig example

No degreasing or kitchen deep clean clip is published on the site, so these are labelled as format and rig examples. Request a sample to see delivered files. See stereo sample page, stereo + wrist-cam example videos, request an egocentric data sample.

FAQ

Egocentric kitchen degreasing data, answered.

What is egocentric kitchen deep clean and degreasing data?
First-person video of a person spraying degreaser, scrubbing and rinsing hoods, walls and counters, and emptying and scrubbing fryers, hoods, floors and shelving in a commercial kitchen, with hand pose and synchronized streams alongside.
Which catalog rows cover it, and what is their status?
Two rows in Restaurant & Commercial Kitchen. "Degrease and scrub kitchen surfaces using degreaser and scrub pads" is Easy and Active collection, and "Restaurant Kitchen Deep Clean" is Medium and Ready to deploy. Both list a head-mounted phone or multiview rig. This page claims no volume or hours.
Is this stereo capture?
Not on the rows. Stereo applies only through the general stereo offer, agreed in the skill spec and confirmed on a Spec Pilot. The stereo kitchen deep clean and degreasing page covers that route.
Is there an off-the-shelf kitchen deep clean dataset?
This page does not claim one. It is custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs.
How does it handle wet and reflective surfaces?
The site states that wet and reflective surfaces degrade active-stereo depth, and kitchen captures ship per-frame depth confidence maps so low-confidence regions can be masked. Behaviour on a given hood or fryer is Not stated.
How are faces and kitchen staff handled?
The site states that faces, plates and screens are blurred irreversibly in every delivered episode, and footage that cannot be de-identified is discarded. Who may be in frame is agreed in the spec.
How fast is a first batch, and who owns the data?
Where coverage is deep, the median time from signed spec to first validated batch is a median of 48 hours; thin coverage runs three to four weeks. The buyer owns the dataset under a perpetual, irrevocable, non-exclusive-by-default licence, with exclusivity available.

Sources

Where are the delivery formats documented?

Request a custom egocentric kitchen deep clean and degreasing dataset.

Tell us the surfaces and appliances and their order, the degreaser, pads, brushes and mops and their start states, the setting, the streams you want and the delivery format your loader expects. We will quote reach, timeline and price against a written spec.