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: TjMakeBot is positioned for teams that want image and point-cloud work managed in one platform, with review and export steps kept close to the project workflow.
Check official docs for: Validate whether your team wants to own self-hosting, upgrades, permissions, and storage operations.
TjMakeBot: The product is designed to let annotators, reviewers, and project owners work in the same environment with clearer status tracking.
Check official docs for: Validate whether your team is comfortable wiring review, acceptance, and delivery into other systems on your own.
TjMakeBot: TjMakeBot emphasizes review steps, issue follow-up, and approval checkpoints so teams can define a repeatable QA process.
Check official docs for: Validate whether training and export will still be handled by your own platform or scripts.
TjMakeBot: Exports, downloads, and downstream use are framed as part of the project workflow rather than as separate manual steps.
Check official docs for: Validate whether you have the people and time to operate an open-source stack long term.
TjMakeBot: The product is designed to give internal teams and external stakeholders a clearer view of project progress and deliverables.
Check official docs for: Check how project progress, deliverables, and stakeholder visibility are presented.
TjMakeBot: TjMakeBot can be a fit for teams that want API, callback, or workflow automation choices without rebuilding the whole process around separate tools.
Check official docs for: Check which API, automation, and integration options are available in official documentation.
TjMakeBot: The platform is positioned for teams that need to evaluate deployment options, permission control, audit support, and procurement readiness together.
Check official docs for: Check deployment options, permissions, audit support, and procurement requirements in the vendor's latest documentation.
If this comparison already narrowed the options, the pages below help you confirm pricing, security, product fit, and practical rollout details.
If feature scope is still the blocker, return to the features page and confirm task coverage, collaboration flow, and export options 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 see the product in a more practical flow before buying or migrating, the tutorials page is the fastest place to continue.
Open tutorialsA practical checklist for hosted 2D/3D data production, human review, training/export, and delivery coordination.
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 annotation, review, export, and delivery workflow.
Best for teams deciding how much orchestration they want to own themselves.
Open related comparisonA decision guide for teams comparing a broader data operations 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 annotation toolsets and a tighter platform workflow.
Best for teams weighing governance, procurement, and delivery workflow 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 team 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 workspace strength and a fuller end-to-end workflow.
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.