Skip to content

The Venturi dashboard

app.venturi.systems (SaaS; a self-hosted deployment serves the same app from its own instance host) is where your attributed AI estate becomes something people act on. Every invocation Venturi sees is resolved into the attribution graph, scored for confidence, and materialized into fast, filterable surfaces. The dashboard is how your finance, engineering, security, and leadership teams read those numbers, drill into the evidence behind them, resolve disputes, and turn attribution into chargeback, savings, and adoption decisions.

This section is the guide to the product surfaces. It explains how the app is organized, how to read what each screen shows you, and how to do the things you came to do: defend a chargeback, close a coverage gap, approve an optimization, or hand finance a reproducible export.

What the dashboard is, and is not

  • It is a read-and-decide surface over the materialized attribution index. Tables load fast, every number names its method and freshness, and every result links to the evidence that produced it.
  • It never blocks your AI traffic. The dashboard reads a pre-computed index; it is completely off the AI hot path. Nothing you do in the app changes production inference directly: even an Active (Gate) recommendation takes effect only when your own enforcement point applies it.
  • It changes attribution truth only through an explicit, audited override. Comments, assignments, and disputes are metadata about an attribution; they never silently rewrite it.

How the app is organized

A persistent left navigation puts Overview at the top, then the six business domains, then the platform-level Admin destination. You see only the destinations your role entitles you to: unentitled items are absent, not grayed out. The table includes the target navigation for the optional Sustainability roadmap extension. Its public reference catalog does not establish that tenant energy and carbon calculations are enabled; confirm the scope and verification evidence in your implementation plan.

Domain Decision supported Capabilities
Cost Own, allocate, optimize Value scorecard, Attribution, Forecasting, Governance, Exports, Teams
Adoption Depth, readiness, program evidence Adoption intelligence, Teams, Onboarding, Deployment readiness
Quality Performance and quality-cost Models, Coverage, Invocation feed
Security & Compliance Evidence, risk, liability Compliance, Overrides, Governance, Invocation feed
Capacity Commitments and supply planning Forecasting, Coverage, Deployment readiness
Sustainability Roadmap resource and carbon estimates Public AI Energy Index reference; target Your energy & carbon workflow

Above the domains, Overview is the global entry point: attributed spend, coverage, and the highest-value signals across the whole estate. Below them, the Platform section holds Integrations, which manages provider and telemetry connections, and Settings, which covers your profile, notifications, people and access, and workspace administration. Tenant administration lives at Settings / Admin; the admin console lists its destinations and the three exceptions to the Admin-role requirement.

A capability lives in exactly one domain and is reached from any domain that shares it, never duplicated. Forecasting is a Cost capability that Capacity also uses; Coverage is a Quality capability that Capacity also uses; Governance is a Cost capability that Security & Compliance also uses. Wherever you enter from, you land on the same page and the breadcrumb names the capability’s home domain, so Cost / Attribution reads the same whether you arrived from Cost or from a link elsewhere.

A global command palette (keyboard-invoked) jumps you straight to any entitled page, team, or attribution record: “open attribution evt_…”, “go to team Payments”, “start export”. A global search bar resolves any of the five graph node types, plus models, teams, connectors, policies, disputes, and saved views, returning typed results with deep links and never crossing your tenant boundary.

The guides in this section map to those capabilities:

  • Attribution detail: the evidence drawer and disputes open from Attribution and the Invocation feed; overrides and their review trail are listed under Overrides.
  • Coverage & unknowns: Coverage, including its Unknown spend view.
  • Optimization & adoption: optimization recommendations and verified savings in the Value scorecard, and cohort adoption in Adoption intelligence.
  • Governance & exports: budgets, policies, and governance modes in Governance, and the FOCUS chargeback export in Exports.

The navigation is a presentation over the attribution model, not another graph. The attribution graph has six attribution layers (invocation, service, project, identity, organization, and budget responsibility), stored as five node types (Invocation, Service, Project, Identity, and Organization) plus budget edges: the sixth layer, budget responsibility, is carried by the budgeted_under and billed_to edges rather than a node of its own. The same model drives every domain above: each one is a projection of the attribution graph, not a separate product.

Start here

  • Tour the surfaces

    Learn the screen layout, the time-basis and freshness model, saved views, and how to read any table on the platform.

    Dashboard overview

  • Defend a number

    Open the evidence drawer behind any attribution, file a dispute, and propose an audited override.

    Attribution detail

  • Close the gaps

    Read your coverage score, work the Unknown Spend Analyzer, and turn reported unknowns into resolved ownership.

    Coverage & unknowns

  • Save and enable

    Review optimization recommendations and read cohort adoption intelligence.

    Optimization & adoption

  • Govern and export

    Set budgets and policies, build a FOCUS chargeback export, and see your billing basis.

    Governance & exports

Principles the whole app honors

  • Every result carries its interpretation metadata. Wherever you see an attribution (a tile, a table row, a drill-down leaf), it carries its stage origin, output state, coper confidence and band, evidence basis, model version where inference was involved, result source, degradation state, freshness, and export eligibility. See confidence and evidence.
  • Unknown is shown, never hidden. Spend Venturi can see but cannot responsibly assign renders as an explicit unknown: an em dash placeholder, never a fabricated $0.00.
  • Method and freshness are always labeled. A figure is marked estimated or reconciled, and stamped with the time it was current as of. Two tiles that name “total AI spend” for the same scope always reconcile to the same figure.
  • Access fails closed. Authentication, role checks, exports, billing, and residency routing all fail closed. Only the decision-time interceptor fails open: on any error or timeout, it forwards your AI request unmodified.
  • No prompt or completion content is ever shown, because none is ever stored. See trust & security for the content boundary.

Who uses which surface

If you are… You mostly live in…
FinOps / Finance Overview, Cost / Value scorecard, Cost / Forecasting, Cost / Governance, Cost / Exports, and Settings / Admin / Billing (read-only)
Platform / VP Engineering Adoption / Teams, Quality / Models, Quality / Coverage, Cost / Forecasting
An engineer resolving a number Cost / Attribution, Quality / Invocation Feed, Quality / Coverage
CTO / CHRO / People leadership Adoption / Adoption intelligence, Adoption / Deployment readiness, scheduled reports
Security / Audit Security & Compliance / Compliance, Security & Compliance / Overrides, Cost / Exports, and Settings / Admin / Audit log (with an Auditor grant or the Admin role)
Sustainability reporting Public AI Energy Index reference; roadmap Your energy & carbon workflow, subject to tenant scope and verification
Tenant Admin Settings / Admin (users, roles, security, credentials, audit), Integrations

You can complete your role’s core task without a Venturi engineer interpreting it for you: that is the bar every surface is built to.

Where to go next

Give feedback on this page

Sign in to send feedback. Opens in a new tab.

Copy page details 
Docs feedback: The Venturi dashboard
Page: https://docs.venturi.systems/dashboard/