AuraOne / Pricing
Loading pricing.
Preparing engagement structures and program scope options.
AuraOne / Pricing
Preparing engagement structures and program scope options.
AuraOne / Pricing
Every engagement starts with the workflow, the required result, and the volume behind it.
Build costs are scoped up front. Each engagement gets a clear quote; recurring pricing follows whether AuraOne runs the work or your systems use the automation directly.
Engagements
Pick the result you need. The quote follows the work behind it. Design partnerships are the way into a new workflow, not a separate product.
Every engagement is a scoped quote. No rate card, no tiers.
Data production
Create expert, voice, or physical-world data against a defined acceptance standard.
Define, build, prove
Run one recurring workflow, then scope a task-specific candidate when accepted outcomes, rights, and evaluation evidence support it.
AuraOne runs it
Send AuraOne the work. We run the workflow and return the finished result.
Your systems use the scoped model
Accepted workflow outcomes become a task-specific candidate, served through a scoped endpoint or approved integration when the evidence supports it.
Side by side
Implementation comes first. Once the workflow is proven, the recurring unit follows who runs it.
| Capability | Human Data program | Enterprise Intelligence implementation | Managed deployment | Dedicated task-model deployment |
|---|---|---|---|---|
| Primary unit | Accepted data units or releases | Implementation milestones and handoff | Completed or accepted workflow outcomes | Task-model executions, endpoint or inference usage, and throughput |
| Initial commitment | Program design and scoped delivery | Define, build, prove, and deployment plan | Operating commitment and delivery capacity | Task-model deployment, integration, and support commitment |
| What you receive | Contracted dataset and documentation | Working task system and baseline evidence | Finished outputs and run reporting | Structured result, version, and exception handoff |
| Availability | Scoped by modality and capacity | Design-partner entry path | Customer-specific managed operation | Design-partner scoped until production proof |
How a quote is built
AuraOne quotes the work required to deliver an accepted result. We publish ranges only after real delivery economics support them.
Agree what goes in, what comes out, which systems are touched, and what counts as correct.
Price workflow design, data preparation, model selection or adaptation, integration, testing, and deployment work.
Write down whether AuraOne runs the work or your systems use the automation, including the unit and handoff.
Other ways in
One commercial starting point. The brief fixes the workflow, the acceptance bar, and the deployment boundary before recurring pricing begins.
Bring one recurring workflow. AuraOne defines the job, establishes what correct means, and builds the first working version.
Bring the current system, its costly failures, and approved corrections. We measure an improved version against the baseline.
The design partnership is the implementation path for a new workflow, not a separate product SKU. It ends in a deployment decision.
Foundry work is scoped in conversation, not from a rate card.
A bounded first climb, a scoped improvement engagement, then continuous hill-climbing across releases.
Talk to us about a climbLicense a sealed evaluation, add improvement material, or pair both under one scope.
Talk to us about a licenseStart a program
Tell us what data your AI system needs or which recurring workflow your enterprise already performs. AuraOne will carry that context into the project brief.