Autonomous Driving DataOps
Best for multi-sensor perception production, QA, version tracking, and customer delivery in teams that already manage complex driving-data workflows.
Pricing
Choose the infrastructure plan that matches your data-production maturity
This is not just a feature-price matrix. It helps autonomous-driving and embodied-AI teams decide whether they are still validating the path, improving individual throughput, or already entering review, version gates, delivery, and procurement.
Current plan status
Current plan：Free Studio
Sign in first to compare your current plan against the next upgrade boundary.
Start with market and maturity, not isolated feature names
Whether you work on autonomous-driving perception data or embodied-AI task data, the first question is not feature count, but whether the workflow, quality, version, and delivery layer is complete enough for the team.
Embodied AI / Humanoid DataOps
Build data production, human review, versioning, and delivery infrastructure now so it is ready before robotics developers scale up.
Review + Version Gate + Delivery
What usually triggers an upgrade is not annotation alone, but whether quality control, version gates, delivery summaries, and audit actually exist.
Free: validate the smallest workable workflow and data-production path
Pro: run AI pre-labeling, training, and export for individual or small-team work
Team: add multi-person review, version gates, delivery summaries, and audit
Enterprise: handle procurement, private deployment, permissions, and integration
Self-serve
Free Studio
Use core 2D/3D annotation tools to validate workflow, dataset standards, and export boundaries before committing the team to the infrastructure.
Best for validating the smallest workflow, tutorials, and small pilot datasets.
Self-serve
Free
Start
- 2D/3D manual annotation and basic export
- New-user AI credits with a limited AI trial
- Does not include team review routing, role governance, or private deployment
Pro
Pro Workflow
For autonomous-driving or robotics data production led by one person or a small team, with AI pre-labeling, cloud training, and model export, but without shared review, version gates, or delivery governance.
For individual- or small-team production work without team governance.
- AI pre-labeling and cloud training
- Model export and training monitoring
- Best fit for individual-led production workflows
Team
Team Review Cloud
For collaborative delivery teams that need team management, role controls, task routing, version gates, delivery tracking, customer handoff, and quality control.
For multi-person review, routing, version gates, and delivery governance.
- Team management and role controls
- Multi-person review, task routing, version gates, and delivery tracking
- Quality control, customer delivery views, and collaborative audit flows
Enterprise
Enterprise Plan
Best for private deployment, SSO, audit controls, dedicated support, and enterprise procurement.
For private deployment, security controls, procurement support, and deeper integration.
Enterprise
Custom quote
Contact sales
- Private deployment and tenant isolation
- Audit controls, permission governance, and SSO
- Enterprise support, contracts, and custom billing
- API, webhook, and integration planning for enterprise rollout
Choose Team Review Cloud or route directly to Enterprise
Use Team when you want hosted review, delivery, and audit in the cloud. Use Enterprise when private deployment, procurement, or integration boundaries become hard requirements.
Team Review Cloud
Stay on the hosted path when you need shared review, dataset versions, release delivery, and customer handoff without adding private infrastructure.
Hosted collaboration with review routing and issue handling
Dataset version, release, delivery summary, and audit workflow
Best when the buying decision is about team throughput instead of infrastructure
Enterprise route
Take the enterprise path when the buying discussion moves into security review, procurement, tenant boundaries, or external system integration.
Private deployment, permissions, audit scope, and procurement alignment
SSO, contract review, and integration planning for API or webhook requirements
Best when package fit depends on deployment and security requirements, not just seat count
Enterprise path
What enterprise inquiry should solve before procurement
Use the enterprise route to confirm deployment boundaries, audit expectations, and integration scope first, instead of forcing those questions into a self-serve package decision.
Clarify whether hosted Team Review Cloud is enough or private deployment is required.
Confirm audit, permission, SSO, and procurement requirements before contract review.
Scope API, webhook, and system-integration needs for rollout instead of guessing from pricing alone.
Clarify the free-tier boundary before deciding the upgrade path
Many pricing pages fail not because of price itself, but because they do not clearly explain what free covers, when to upgrade, and how enterprise needs should be routed.
Free Studio boundary
This is not an unlimited forever plan. It is the entry point for evaluation, tutorials, and the smallest workable project path.
Best for validating a solo 2D/3D annotation path.
Best for trying AI and export rather than sustained high-frequency production.
Once you need review routing, collaboration, and steadier delivery rhythm, it is time to upgrade.
When to move to Pro or Team
One of the most important pricing decisions is whether the current bottleneck is solo throughput or collaboration throughput.
Choose Pro when AI pre-labeling, training, and export matter but work is still individual-led.
Choose Team when multi-person handoff, review, and quality control become normal.
If users are already asking who reviews and who hands off delivery, Free is usually no longer enough.
What the enterprise inquiry path should solve
Enterprise is not just a bigger plan. It is a separate path for private deployment, compliance, procurement, and contract support.
Best for teams that need private deployment, SSO, audit, and permission boundaries.
Best for enterprise customers that need procurement support, contracts, and custom billing.
The pricing page should make it explicit that these users should inquire directly instead of guessing package fit.
Three quick checks before you buy
For evaluation, tutorials, and a small pilot, Free Studio is usually the right starting point.
If your project is individual-led and needs AI pre-labeling, training, and export, Pro Workflow is the better fit.
If you need team management, multi-person review, and quality control, move to Team. Use Enterprise for private deployment and procurement.
Pricing
Choose by project stage, team size, and delivery needs
Start with Studio for evaluation, move to Pro Workflow for individual-led production, and choose Team or Enterprise when you need governance, review routing, private deployment, or procurement support.
Pro fits individual-led AI pre-labeling, training, and export.
Team earns its place when review routing, version gates, delivery summaries, and audit start to matter.
If the team is already asking who reviews, which version can freeze, and how delivery is handed off, Free is no longer the right boundary.