AuraOne
Pricing

Pricing that stays legible.

Every plan includes the full platform. Pricing scales with your program, not your ambition.

Four plans. Clear scope.

Start with one workflow. Expand when the evidence confirms it.

Starter

For teams evaluating AuraOne with a focused pilot.
Contact
for details
  • Platform walkthrough and guided onboarding
  • Core evaluation and evidence workflows
  • Security review kit on request
Most common

Team

For teams scaling evaluation, review, and governance.
Custom
by usage
  • Multiple workstreams and environments
  • Workflow templates and quality gates
  • Dashboards and evidence exports

Enterprise

For regulated deployments with procurement and compliance requirements.
Custom
annual
  • SSO and provisioning support
  • Retention and export configuration
  • Deployment architecture review

Program

For defined programs with evidence requirements and delivery milestones.
Custom
statement of work
  • Joint success criteria and checkpoints
  • Implementation plan with runbooks
  • Executive review cadence

All plans priced per program. "Contact" means we scope your specific needs and give you a number within 48 hours.

Self-serve billing

Spend stays legible.
Procurement stays calm.

Plans, quotas, credits, and procurement workflows are first-class. No spreadsheets. No surprises. Just enforceable limits with receipts attached.

Credits, Quotas, Procurement
Credits wallet
active
balance
$3,483
Usage ledger-backed credits (example), not estimates.
ledger
Credits purchased
+$5,000
AI Labs eval usage
-$412
Workforce QA hours
-$980
Overage auto-approved
-$125
Quota controls
soft limits
Evaluations68%
this month
Workforce hours42%
this month
Synthetic runs57%
this week
Transparent, enforceable billing
Plans, quotas, credits, and procurement sit in the same system—so finance sees the same truth engineering ships.
API surface
GET /api/v1/billing/credits
GET /api/v1/billing/quotas
POST /api/v1/billing/procurement
GET /api/v1/billing/plans
Procurement workflow

Approvals without the
back-and-forth.

AuraOne ships procurement as a product surface: packets, routing, and evidence—so enterprise buying feels as calm as self‑serve.

Procurement workflow

Procurement that doesn't slow product.

Generate the security packet. Route approvals in parallel. Attach evidence. Activate credits. Average time from request to activation: 48 hours.

TermsNet-30 + PO
Procurement request
AuraOne - Team Plan
Scope is explicit. Evidence is attached. No back-and-forth email thread.
ETA
Same day
Buyer
Your organization
Start date
Upon PO acceptance
Billing
Net-30 with PO
Security review
Packet included (no extra request needed)
Vendor profile (auto-generated)
W-9 / business detailsIncluded
Security questionnaireTemplate
DPA / SCCsProgram-defined
SOC 2 reportBy request
Evidence included at every step

Reviewers see the same evidence pack AuraOne generates in production: model cards, datasheets, audit trails, and signed exports.

Spend stays predictable

Credits and quotas are enforced in the platform. Approved spend stays matched to actual usage, with alerts before you hit limits.

Common questions

Short answers. No surprises.

Do you publish a fixed price list?

Pricing depends on program shape: environments, workflows, throughput, and governance needs. We keep the structure predictable and the spend legible, but one-size-fits-all numbers do not work for high-stakes programs.

How does procurement work?

We generate a security review packet, a scoping document, and procurement materials upfront. Enterprise agreements use standard terms and an evidence pack your reviewers can share internally.

Is there a self-serve path?

Yes. Teams can start with a focused pilot, validate one workflow end-to-end, and expand when the evidence chain is confirmed. Procurement and SLAs are available when required.

Can we run a security review before signing?

Yes. We can share a security review kit (architecture diagrams, controls overview, and questionnaires). Formal attestations and reports depend on engagement and deployment model.

What does a typical rollout look like?

Start with one workflow and one suite. Validate outputs and evidence in staging. Then expand to additional modules as the operating model stabilizes.

Tell us what you're building.

We'll send a scoped proposal within 48 hours.