Vision & Physical AI

Training data and live review for models that see and move.

Robots, vehicles, vessels and inspection models trained on images, video and point clouds a person has checked, then watched in production.

What we label

Every annotation type we deliver, drawn on the kind of data it belongs to. Each class goes into a guide written with your team before the first batch.

Sample frame. Point at an annotation type to see it on the frame.

Still frames from cameras, phones, drones and scanners.

  • Bounding boxes

    Objects boxed tight to the edge, with occlusion and truncation flags.

  • Polygons and masks

    Instance and semantic segmentation with pixel accurate edges.

  • Keypoints and pose

    Skeletons for arms, people and hands, and grasp points on objects.

  • Polylines

    Edges, rails, cables, cracks and boundaries.

  • Classes and attributes

    Frame level tags such as scene, lighting, clutter and quality.

  • Captions

    Plain language descriptions for vision language models.

Delivered asCOCO JSON, YOLO, Pascal VOC, PNG masks or your own schema

What we do for vision teams, from the first file to the live model

  1. Collect

    Data collection

    Robot episodes, site photos and drive footage collected to a brief.

  2. Annotate

    Detection and segmentation

    Boxes, polygons and masks, from a few classes to long tail taxonomies.

    Video and tracking

    Tracks with stable IDs, events and actions, frame by frame.

    Point clouds and fusion

    Cuboids and segmentation aligned across camera and LiDAR.

    Robot learning data

    Episodes, grasp points and task descriptions.

  3. Test

    Model testing

    Predictions checked against the source, errors typed, results split by condition.

  4. Review live

    Live review

    Low confidence detections confirmed or corrected by a person in under 2 minutes.

Every correction from testing and live review goes back into the next round of training.

How we test vision models

People check what your model predicts, on your data, and tell you where it fails.

Prediction validation

Predictions from your detector or segmenter checked against the image. Every error is typed and corrected, and the worst items go back for full relabelling.

What you getCorrected data, precision and recall by class, and an error gallery

Robustness by condition

Hard conditions tested on purpose: low light, rain, glare, fog, motion blur, rare classes and unusual angles.

What you getResults split by condition, with the gaps spelled out

Evaluation sets

A held out set built from your own data, labelled to the guide and versioned, so every release is tested the same way.

What you getA versioned test set with a changelog

How evaluation works

What the work looks like

Client E, Client D and Client H run our reviewers inside their live vision pipelines.

Every object labelled to your class guide

Boxes, masks, keypoints and tracks drawn in our workspace or yours, then checked by a second reviewer.

Annotate services
Frame 412 on a phone: four labelled boxes, the labels list and a QA pass.Labelling workspace on frame 412 of a robot pick and place set: four labelled boxes, grasp_target with a keypoint, bottle_squeeze selected, a labels list with shortcuts and a QA pass from the second reviewer.
Sample data, shown in our labelling workspace. We also work in CVAT, Label Studio, Roboflow and your own tools.

Works in

CVATLabel StudioRoboflowLabelboxEncordV7SuperAnnotateSuperviselyyour own tool

Delivers

COCO JSONYOLOPascal VOCKITTIMOTPCDmasksyour own schemato S3, GCS, Azure or SFTP

Checks

Class guide signed off before the first batchSecond reviewer on every itemWeekly agreement against a gold setSampled before delivery, every label logged

Questions vision teams ask

Do you annotate LiDAR and point clouds?

Yes. 3D cuboids, point segmentation and tracking across sweeps, linked to the camera frames when you have them.

Can you work in our labelling tool?

Yes. CVAT, Label Studio, Roboflow, Labelbox, Encord, V7, SuperAnnotate, Supervisely or your own tool. We can also set one up in your cloud.

What formats do you deliver?

COCO JSON, YOLO, Pascal VOC, KITTI, MOT, PCD, masks or your own schema, delivered to S3, GCS, Azure or SFTP.

How do you handle edge cases?

Every hard case goes into the class guide with an example. A senior reviewer settles disagreements, and the guide is versioned so you can see what changed and why.

Can you review our model in production?

Yes. Low confidence detections route to a reviewer who confirms or corrects them in under 2 minutes, 24/7, and every correction comes back as training data.

How is our data protected?

Every annotator works under NDA, we work inside your access controls where we can, and data can stay on EU servers.

How do we start?

Send a small batch. We label it free and send it back, usually within 24 to 48 hours, so you can judge the work before you commit.

Send us the frames your model gets wrong

Send a small batch and get it back done, free, usually within 24 to 48 hours. You judge the work before you pay for anything.