Skip to content

AI Governance

Know exactly where your AI budget is going. Every token, every seat, every API call — tied to a person, a team, a project, a cost centre, an outcome.

Most tools tell you what happened last quarter. Flowstate tells you what is happening, why, and gives you the controls to do something about it. Stop flying blind. Then stop the leaks.

This is the AI Governance pillar — one of three in Flowstate (alongside Workforce Engineering and Finance & Compliance). It runs on telemetry from the Flowstate Agent on developer machines, plus authoritative billing pulls from your providers.

Flowstate covers coding tools first-class today and is expanding across image, video, audio, sales, marketing and legal — see the Catalog for what's visible right now.

What's in here

Insights — what your AI estate is actually doing. In the app: Insights → Agent insights (Dashboard · Spend insights · Agent sessions · Alerts).

  • Attribution — every prompt, seat and API call resolved to a person, team and project.
  • Spend reconciliation — provider invoices matched against observed usage, Xero-style.
  • Forecast — spend projection by project, team and planned Agent, with confidence.
  • Fluency — how well your engineers describe, delegate, discern and verify with AI.

Agentic workforce — the AI workers you plan and resource. In the app: Resourcing → Agentic workforce (Agents · AI tools · Models · Rules).

  • Agentic workforce — the agentic-team lens in one page.
  • Agents — planned AI workers with an owner and a catalogue model, forecast by runs.
  • Models — the model catalogue Agents reference for pricing and capability.
  • The AI cost model — copilot spend loads onto the person; agent spend gets its own line.

Governance — the controls.

  • Alerts and signals — behavioural-signal stream covering content safety, brand and usage, budget, and operational categories.
  • Detected services — the AI services Flowstate has observed traffic for in your org, and who's using them.
  • Usage providers — provider billing connections for authoritative spend, connected from the Integrations marketplace.
  • Policy and enforcement — active policy, drafts, version history and audit log.
  • Service accounts — production AI workloads governed separately from people.

Agent — the on-device sensor.

  • Agent overview — install paths, two pathways (Telemetry vs Enterprise), how the agent ships.

Cloud Proxy — network proxy routing and per-subject attribution for managed fleets.

Self-service — what your engineers see in their own session.

  • My AI — personal standing, sessions, the tools you use, and the Request centre for seat and tool requests.

Admin and connections — the pipes.

How it fits together

Read Concepts for the telemetry → signals → policy loop in one page. Then pick the deployment pathway that matches your AI estate at Telemetry vs Enterprise.

We're an insight and policy layer. Not a reseller. Not a billing middleman. We don't touch the money — we just make sure you can see where it's going and decide what to do about it.

Flowstate Documentation