Use this page to decide whether your team wants full control over a self-hosted open-source tool or a managed path that keeps annotation, review, training/export, and delivery together.
TjMakeBot: One hosted workflow for 2D images, 3D point clouds, human review, training/export, and delivery.
Validate the alternative: Validate whether your team wants to own self-hosting, upgrades, permissions, and storage operations.
TjMakeBot: Human review, delivery summaries, downloads, and version context stay on the same delivery path.
Validate the alternative: Validate whether your team is comfortable wiring review, acceptance, and delivery into other systems on your own.
TjMakeBot: Training, export, result summaries, and downloads can stay attached to the same hosted workflow.
Validate the alternative: Validate whether training and export will still be handled by your own platform or scripts.
TjMakeBot: The main site owns security, audit, permission, and handoff boundaries for production teams.
Validate the alternative: Validate whether you have the people and time to operate an open-source stack long term.
If this comparison already narrowed the options, the pages below help you continue with budget, security, feature coverage, and hands-on validation.
If capability coverage is still the blocker, return to the features page and validate the 2D/3D, review, training/export, and delivery path in one place.
View featuresIf budget, packaging, or procurement timing is the real blocker, the pricing page will move the decision faster than another abstract comparison.
See pricingIf your team cares most about boundaries, deployment, audit, and permissions, the security page is the better next checkpoint.
Review securityIf you want to validate the real operating path before buying or migrating, the tutorials page is the fastest proof route.
Open tutorialsA practical checklist for hosted 2D/3D data production, human review, training/export, and delivery handoff.
Best for teams choosing between image-first tooling and a broader production workflow.
Open related comparisonA checklist for teams comparing flexible task configuration with a tighter train-export-delivery loop.
Best for teams deciding how much orchestration they want to own themselves.
Open related comparisonA decision guide for teams comparing a broader data-ops platform with a hosted delivery workflow.
Best for teams balancing platform control, self-hosting preference, and delivery speed.
Open related comparisonA comparison for enterprise teams choosing between governance-heavy labeling layers and a tighter hosted workflow.
Best for teams weighing governance, procurement, and delivery path together.
Open related comparisonA guide for teams deciding between managed labeling services and a self-serve SaaS production path.
Best for teams deciding whether to keep production outside or bring it closer to the internal workflow.
Open related comparisonA checklist for teams comparing image/video-first tooling with a broader 2D/3D delivery workflow.
Best for teams deciding between visual-workbench strength and a fuller production-to-delivery path.
Open related comparisonNot exactly. It is a better fit when you want a managed delivery workflow rather than a stack you operate yourself.
Keep evaluating CVAT when open-source, self-hosting, and infrastructure control are explicit requirements your team can sustain.
The biggest tradeoff is whether your team wants to keep operating the platform layer and integration complexity itself.
Map who owns operations, audit, and delivery first, then decide whether your team should keep that complexity in-house or move it into a managed workflow.