You are already paying for human data and AI work. The difference here is what you keep: reviewed data, rights terms, review notes, test results, and handoff files. Robotics pilot bands and every other scope are quoted to the work.
100 to 500 reviewed episodes. A fundable first step.
WHAT YOU KEEP
Your data. Your record.
The contracted data, review notes, test results, and handoff files.
A REAL FIRST STEP
Four plans. One number, fast.
Start where it costs you today. Robotics pilot bands are quote-scoped after the episode target, modality, review depth, and delivery format are confirmed. A human-data quickstart starts on one queue you are already paying to run elsewhere. Public pricing copy is a planning guide only. Final pricing, support targets, entitlements, and usage terms require a signed quote, order form, or statement of work.
QUICKSTART
Quickstart
Start on one queue you are already paying to run elsewhere.
Quote scoped
robotics pilot: 100 to 500 reviewed episodes
Quote scoped. Contract scoped.
What this plan runs
One queue you already pay to run
SCOPED
PLATFORM
·One queue, one data type, one team
·Robotics pilot band is quoted during scope review
COLLABORATION
·Calibrated reviewers
·Shared review inbox
GOVERNANCE
·Measured against the vendor line item you pay today
·Cycle time, review quality, overrides, regression capture
The two sides are not priced by the same unit, so we state both plainly. Human Data is priced around expert training data. App Data is priced around the app, input batch, source systems, and output your team needs back. Model it before you call. Buy both and it lands on one quote.
HUMAN DATA
Priced by data program
You pay for the expert data your model needs: the data type, the expert depth, the review bar, and the usage rights.
APP DATA
Priced by app
You pay for the app, input batch, source systems, and output your team needs back.
BUY BOTH
One quote
AI labs and robotics teams often need both. Build the training data. Test the launch work. One scope, one quote.
COMPARE PLANS
Where the plans differ.
Feature comparison across AuraOne pricing tiers
Feature
Quickstart
Team● RECOMMENDED
Enterprise
Program
Environments
1
Multiple
Multiple + private review
Multiple + private review
Reviewers
Small named group
Reviewer groups
Role-based, with SSO
Role-based, with SSO
Workflow templates
Not scoped
Scoped
Scoped
Scoped
Reviewed record exports
Starter record set
Standard exports
Review-ready record
Program reporting
Regression bank of caught failures
Not scoped
Scoped
Scoped
Scoped
Reviewed data and records you keep
Not scoped
Scoped
Scoped
Scoped
Audit and retention controls
Not scoped
Policy review
Expanded policy
Program policy
SSO and directory sync
Not scoped
Not scoped
Scoped
Scoped
Data residency
Not scoped
Not scoped
Set in the contract
Set in the contract
Named implementation partner
Not scoped
Success partner
Named partner
Implementation owner
Support response
Business hours
Response targets
Escalation path
Escalation and cadence
Joint rollout plan
Not scoped
Not scoped
Not scoped
Scoped
WHAT YOU KEEP
An asset you own. Not a rental.
Rent the intelligence and you re-buy the same capability every cycle and keep nothing. Here the spend becomes something you hold. The EU AI Act high-risk provenance rules enforce in August 2026 — clear provenance is a line item to fund now, not after.
HUMAN DATA
A chain of consent
Every datapoint carries who created it, who reviewed it, and the rights it was collected under — an identity-verified record that survives an audit. You take the dataset with you.
REGRESSION BANK
Every caught failure
A bank of every failure the review loop caught, kept so the same mistake is caught again. It is yours, not a vendor's.
YOUR RECORD
Reviewed work, usable later
A reviewed record with notes, checksums, test results, and scoped handoff terms. When the term ends, you keep the work instead of re-buying a black-box report.
PROCUREMENT READINESS
The six things procurement needs to see.
Security readiness. DPA. MSA. Residency. Subprocessors. A quote-scoped band. Answered in order, up front — not at the end of the cycle.
01
Security review materials
Controls matrix and available security evidence. Formal report status, auditor, scope, exceptions, and dates are shared only when a current attestation is available in the review packet.
↳ READINESS
02
DPA
Data processing terms, SCC scope, and subprocessor review are handled through procurement.
↳ AGREEMENT
03
MSA
Master services agreement. Reviewed redlines turn into a signed paper trail, not a maze.
↳ AGREEMENT
04
Residency
Region of record, evidence location, reviewer location, and export path, set in the contract by deployment.
↳ POLICY
05
Subprocessors
Named list, purpose, region, update cadence, and notification terms, shared during review.
↳ LIST
06
Price band
Robotics pilot bands are quote-scoped after episode target, modality, review depth, and delivery format are confirmed. A human-data quickstart starts on one queue you already pay to run. Answered first, not last.
↳ QUOTE
REVIEW PACKET
One brief for the whole table.
Procurement, legal, and security review the same record at the same time, instead of three rounds in sequence.
REQUESTACCEPTED QUOTE
BEFORE YOU CALL
The questions worth asking.
How long is the term?
A quickstart runs short, on one queue or a robotics pilot. Team, Enterprise, and Program move to an annual or multi-year agreement. The exact term is set in the contract.
Is there a minimum commitment?
The smallest commitment is a single pilot: a robotics pilot scoped around the target episode count and review depth, or one human-data queue you already pay to run.
How does the bundle quote work?
Human Data is priced around expert training data. App Data is priced around the app, input batch, source systems, and output your team needs back. Buy both and the two land on one quote.
What happens to my data and evidence record at the end of the term?
You keep the contracted data, review records, test results, and handoff files defined in the scope. You bought work your team can use, not a black-box rental.
PRICING
Tell us what you want to run.
Name the queue or workflow. We map it to a plan and a number, fast.