Skip to content

Known limitations

This page is Venturi's known-limitations register — the single, maintained list of what the platform cannot capture, how it behaves when a component degrades, and which controls or attestations are not yet generally available. It exists because stating ambiguity plainly is the system doing its job: Venturi would rather tell you "we cannot see this" than render a confident number that cannot be defended.

How to read this register

Each entry names the limitation, the honest behavior you will observe in the product, and the path that narrows or closes it. Nothing here is euphemised: an uncapturable pathway is called uncapturable, a fallback result is labeled a fallback, and an attestation Venturi does not hold is stated as not held. Release-state labels on this page follow the binding index in Docs authority & product state.

Uncapturable and detected-only pathways

Venturi attributes what it can observe. Some routes AI spend takes through an enterprise estate cannot be resolved at request granularity with the integrations you have connected — and some cannot be resolved at request granularity at all. These pathways are never silently absorbed: they surface as named output states and as entries in the discovery ledger, and they stay out of the chargeback denominator.

Pathway Limitation Honest behavior What narrows it
Shadow AI — unsanctioned tools or personal accounts Not attributable at request granularity; detectable only via CASB, DNS, or admin-API signals Held as a detected-only line in the discovery ledger with first/last-seen dates and a labeled activity estimate — never an invented dollar figure, never billed Connect detection sources (CASB, DNS) so detection improves; attribution requires the traffic to move onto an observable pathway
Client-side calls — browser or desktop calls that bypass your gateway Visible, if at all, only in aggregate provider billing Resolves to not_identifiable; counted against the 100% pathway-coverage target, never assigned to the nearest team Route the calls through your gateway or send InvocationEvents
Opaque SaaS-embedded AI — vendor features that expose no per-call usage The vendor's plan does not expose AI-specific consumption Shown as bounded or detected-only with the limiting vendor named; excluded from chargeback Vendor admin-API connectors where the vendor exposes usage; otherwise this is a genuine limit
Uninstrumented direct provider calls Calls that reach a provider by a path with no connector or event coverage Spend appears as an honest unknown with the reason Uncaptured pathway in the Unknown Spend Analyzer Extend connector or gateway coverage; the coverage map names the would-close integration
Total-estate completeness without an independent anchor Where no external spend anchor (cloud billing AI line items, GL categories, invoices) exists, total-estate coverage cannot be verified The coverage report states the figure is "measured against the instrumented estate only; total-estate completeness is unverified" Provide an independent anchor so Capture Coverage % is measured against your real estate

Fallback and degradation behavior

Behavior What happens How it is labeled
HeuristicBaseline fallback If the trained model cannot answer inside its 20 ms wall-clock budget — or is unavailable — a deterministic, conservative heuristic answers instead so your AI traffic is never blocked The result carries an explicit result source marker (heuristic baseline, not trained model) plus a degraded flag, unchanged even when the heuristic is confident; the serving state shows degraded_serving
Fallback results and money A fallback attribution is excluded from the savings counterfactual and adoption cohort rollups, and should be excluded from chargeback until re-observed under trained-model attribution Filterable by the result-source marker in dashboards, exports, and the API — see Confidence & evidence
Provisional and demoted attributions Calibration drift or model age can demote an edge from Chargeback-ready; demotion is automatic, re-promotion never is The evidence card records the demotion reason; demoted edges leave the chargeback base visibly
Confidence is capped Operational confidence (coper) carries a deliberate policy ceiling of 0.95 — Venturi never reports certainty Only coper ≥ 0.80 is chargeback-eligible; everything below is analysis-only

Controls and attestations not yet generally available

The binding release-state index for every enterprise control is Docs authority & product state. The entries below are restated here because a reviewer reading only this register must still get the honest picture:

  • SOC 2 is not yet held. Type I readiness/report is a target on the security roadmap; Type II is targeted within 12 months of Type I. No page on this site implies otherwise. See Compliance → SOC 2.
  • The identity-enforcement layer is Target-state. RBAC/ABAC runtime enforcement, SSO/SCIM/MFA enforcement, record-level tenant-isolation enforcement, and support break-glass enforcement are defined but their uniform fail-closed runtime is still being wired.
  • The 99.95% availability step-up and the 15-minute Sev-1 MTTA target are milestone-scoped to Venturi's first dedicated on-call coverage window and are not advertised before it. See Support.
  • ISO 27001, ISO 42001, and FedRAMP are not held and are stated as roadmap or out-of-scope rather than implied. See the control framework crosswalk.

Documentation boundaries

  • Connector setup guides are release-state scoped. Cloud accounts (AWS, Google Cloud, Azure), the ingestion API and drop-in proxy, and the source-system connector catalog have setup guides. Discovery-only connectors, including CASB, DNS/firewall, and optional eBPF passive capture, remain labeled as discovery evidence and do not imply request-level attribution or chargeback readiness.
  • Model cards are not yet GA. The consolidated AI-transparency page and model-card index are published, but the decision-time adapter's model card remains a Phase-2 model-ops deliverable and is not advertised as GA.