Skip to content

30-minute quickstart

Outcome 1 attributable record From 1 connected evidence source.
Target time ≤30 minutes No Venturi-human response or emailed setup value.
Verify in Quality feed Inspect source, mapping, evidence, unknown state, and freshness.
Open guided setup

Product availability: Available now. An authorized developer, Engineer, or Admin can move from tenant creation to at least 1 connected evidence source, then make the 1st AttributionRecord visible in the quality feed within ≤30 minutes. The path completes without a Venturi-human response or emailed setup value. Venturi tenant, connector, federation, and external-ID setup artifacts are generated in-product. Customer-provided provider-account credentials are entered in-product. Credentials remain tenant-local and are validated for read-only access.

Every step below runs on a connected evidence source. File import is planned and unavailable today, so no step here depends on it. For SaaS verification, open the quality feed. For self-hosted deployments, use the same /domains/quality/feed path on your own instance host. See Docs authority & product state for the binding release-state index.

What the 30-minute milestone means

Engineering active-use milestone The 1st attributable record from a connected evidence source, verified through the quality feed.
Persona-complete production onboarding Product, Security, Engineering, and Finance complete real in-product actions, and Finance accepts a chargeback-eligible export. There is no admin override and no support override.

Provision the organization

Role: Admin with tenant and identity settings access.

  1. Create the tenant in guided setup.
  2. Configure IdP federation and confirm a test assertion.
  3. Assign the Admin and Engineer entitlements needed for setup.

IdP federation authenticates people to Venturi. It is distinct from the identity-resolution connector that later maps usage to owners and cost centers.

Add evidence

Role: Engineer or Admin with connector settings access.

Register a cloud or provider source. The setup flow generates Venturi connector, federation, and external-ID artifacts. For a provider API, enter customer-provided read-only provider-account credentials in-product. Automated credential validation must pass.

File import is planned and cannot complete this step today.

Map identity and cost

Role: Engineer for source mapping; Admin for role or directory changes.

Connect identity evidence, map account and project dimensions to teams and cost centers, and inspect unmapped values. Preserve unknowns instead of assigning them speculatively.

Deploy

Role: Engineer with deployment access; cloud setup permissions are needed only when creating a cloud connector.

Bash
cd infra/<cloud>/onboarding
terraform init
terraform plan
terraform apply
./scripts/verify.sh

The deployment runs RAIL attribution after the evidence source is ready.

Verify active use

Role: Engineer or authorized viewer with quality-feed access.

Open the quality feed and inspect the 1st AttributionRecord. Confirm its source, identity and cost mapping, evidence, coverage, unknown state, and freshness.

Continue to production onboarding

Support can help recover a failed step, but no support action is required to reach either milestone. See Support.