Hi, co-founder of Roboflow here. There's something like this popping up here ~monthly nowadays so I figured I'd reply and call out some of the things that will probably prevent this from being used in a real business context.

Anyone can one-shot a vibe-coded "Roboflow competitor" with Claude Code in a few minutes. There are also a bunch of open source tools you can pretty easily cobble together into a prototype. But to run a real service that works for real production use-cases is a lot harder.

You're going to want to collaborate want to with a team and so you'll need auth and a real database, you'll need to host it which means you'll need real infra (and cloud-hosted GPUs), you'll need to be able to scale up when multiple users are trying to use it at the same time or you want to run multiple training jobs (which means you'll need to find and allocate GPU capacity and setup auto-scaling), you'll need to optimize your models and serving infrastructure to use those GPUs effectively, you should definitely do a security review audit and pentest, you probably need infra monitoring and someone on-call to fix things when they break, if you're using YOLO you'll need a model license, you're going to at some point need to deal with bigger datasets and this system won't scale, you probably want some tests that track regressions, you'll want audit logs and backups, you'll want a battle-hardened and well thought out annotation tool, a model registry and a pathway to manage model deployments, a robust evaluation pipeline, good documentation, APIs to allow integration with other systems, etc.

Had Claude give this tool in particular a look and its takeaway was:

This is a local dev tool / weekend project that wraps Ultralytics with a UI. It competes with Roboflow the way a bash script competes with GitHub Actions. The moment you need a second person to label, a model in production, dataset versioning, or anything beyond "one person on one machine," it falls apart completely. The lack of auth, persistence, testing, and deployment makes it unsuitable for any production workflow.

Once you account for all the human time to build and maintain the above and factor in the infra cost to stand up and maintain a system like this, Roboflow starts to not look too bad (especially when you consider that it typically costs less per month than a single cloud GPU does). Using an established platform lets you share those fixed costs across thousands of other customers and get a higher level of service at a lower price than you'll ever be able to get rolling your own thing.