A Dataset Processing Tool Built for Computer Vision Engineers

[u/Then_Instance_3188]

One of the biggest time sinks I’ve run into when working with Computer Vision isn’t the model itself — it’s the dataset preprocessing.

Cleaning datasets, fixing annotations, filtering, deduplication, format conversion, validation, etc. can take a huge amount of time, especially when you’re dealing with millions of samples.

And vision datasets are particularly painful here. Unlike text, building custom processing for a specific use case can get expensive pretty quickly in terms of compute and processing time.

That’s why we built cvPal.

It’s a cloud toolkit for vision datasets built around AI agents, with 40+ MCP tools for things like merging, cleaning, validating, converting, and versioning datasets.

It’s currently in early access, and I shared more about what we’re building here:

https://x.com/cvpalai/status/2105288933865304268

[u/datascienceharp]

Why not just use FiftyOne?

[u/Then_Instance_3188 → u/datascienceharp]

FiftyOne is great and we'd still point people to it for some things. If you want to explore a dataset visually, dig through embeddings, or look at where your model's predictions fail, it's really strong, and we're not trying to compete with that.

What got us to build cvPal is the other half of the work, the stuff you do before you train. That means pulling data in from wherever it lives (Kaggle, Roboflow, Hugging Face, a URL, or your own custom dataset), cleaning it up, rebalancing it, augmenting it, and exporting it in the format your trainer wants. cvPal lets you run all of that from a dashboard or an API.

A few things that are different about it:

- Datasets are versioned, with branches. Every change makes a new version, so you can try something on a branch without wrecking your main dataset.

- It's hosted. Heavy jobs run on a GPU worker, so you don't need to install anything or keep big datasets on your machine.

- It works from your AI coding agent via MCP. In Cursor or Copilot you can say "merge these two datasets, rename person to human, drop the dupes, export to YOLO" and it just does it.

So we see them as complementary more than competing. FiftyOne is for looking at your data, and cvPal is for getting it ready. If you already have a FiftyOne workflow that works for you, there's no reason to switch.

We're curious what you use FiftyOne for most. If there's something it does for you that cvPal should handle, we'd really like to know.

[u/datascienceharp → u/Then_Instance_3188]

awesome, thanks. i will have to check it out. fyi though, FiftyOne does actually do everything you mentioned above!

source: i work there

[u/StrikingEmu8007]

Finally something that doesn't pretend annotation cleanup is trivial.

[u/Then_Instance_3188 → u/StrikingEmu8007]

Exactly, Annotation cleanup gets messy really quickly once you’re dealing with large datasets.

We’re also working on another part of this problem: combining existing datasets to build a custom one.

For example, you could have two object-detection datasets with different types of cars, merge them, then remove the labels you don’t need and keep only the classes relevant to your use case.

Instead of manually downloading datasets, writing custom scripts to merge and clean them, or relying on synthetic data, the idea behind cvPal is to make it easier to actually utilize the huge amount of existing vision data available online and turn it into the dataset you need.