DOCS · DEPLOYMENT

Run it yourself. Keep what you own.

Deploy on your your environment. Start with one workflow, confirm the clear provenance trail, then scale with review already in place.

Run it yourself Read docs

RUN IT YOURSELF

Local-first

Deployment scope is agreed before launch. No pooled data. Reviewed records, files, and handoff terms stay with the customer.

FIRST RUN

Get going

Account, API key, SDK install, first run. In that order.

PASS THE REVIEW

Review-ready

Every run exports a clear provenance trail a reviewer can check before you ship.

FIRST DEPLOYMENT · LIVE READOUT

FIRST RUN, QUICKLY

Trust one suite, then scale.

Validate the result. Only scale after the clear provenance trail is clear enough to trust.

STEP 01

WHAT WE START

Stand up the workflow

Request access, pair on review requirements, generate the production API key, install the SDK. On your your environment by default.

→

STEP 02

WHAT WE VERIFY

Confirm the provenance chain

Run the first evaluation. Health monitoring, audit logging, and the handoff file all populate against the same record.

→

STEP 03

WHAT WE SCALE

Expand with review in place

Once the provenance chain is trusted, scale workflows. SLOs, runbooks, and incident response stay attached.

QUICKSTART CODE

The first run is one command.

Install the SDK, set your key, run your first evaluation. The result returns an id, a status, and a clear provenance record you can export.

↳ INSTALL AND RUN

# Install the AuraOne SDK
npm install @auraone/sdk

# Set your API key (from app.auraone.ai)
export AURAONE_API_KEY="your-production-key"

# Your first evaluation
import { AuraOneClient } from "@auraone/sdk";

const client = AuraOneClient.withApiKey(process.env.AURAONE_API_KEY!);

const result = await client.evaluations.create({
  template_id: "rubric.web.qa",
  agent_bundle_url: "s3://auraone-demo-artifacts/web-qa/agent-bundle-2026-05.zip",
  wait: true,
});

console.log("Evaluation complete:", result.id, result.status);

See more examples

INFRASTRUCTURE

What the deployment actually runs on.

The domains a reviewer inspects during deployment review. Bring the question. We'll bring the page.

Compute

Isolated workloads per organization. Autoscaling where supported. Configurable quotas. Predictable performance envelopes.

↳ DOMAIN

Storage

Backups and restore procedures. Caching for low-latency reads. Object storage for exports and proof. Retention and deletion workflows.

↳ DOMAIN

Networking

TLS encryption in transit. Private networking options (plan dependent). Configurable inbound controls. CDN-backed asset delivery.

↳ DOMAIN

Monitoring

Prometheus metrics collection. Common monitoring destinations supported. Health dashboards. Automated alerting via Slack and email.

↳ DOMAIN

DEPLOY ON YOUR TERMS

Run it yourself. Keep what you own.

Deploy on your your environment, or plan a path that matches your constraints and review requirements.

Run it yourself Plan a pilot