Explore Flowstate

The Flowstate platform
Flowstate Helm

Know what AI costs. See what you get back.

Understand spending, share budgets and connect AI use to the work it supports.

Recent insights All insights

Buy tokens, rent GPUs, or own the rack?

Open-weight models are now good enough to make self-hosting a financial question rather than a capability one. I modelled four options, an office rack, colocation, rented GPUs and per-token APIs, to find where each one actually wins. The answer turns on utilisation, and it isn't the one the internet keeps giving.

Turn a $3m AI bill into $1.9m

Most teams overpay for AI twice without noticing: they run everything through the default flagship model, and they buy the tokens on a metered plan they can't see into. An intelligent proxy fixes both. Here is the maths, a calculator you can drag, and where Flowstate fits.

Start with the work All use cases

Understand AI spending and value

See where the budget goes and what the business gets back.

Share one AI budget across your tools

Fund people, teams and projects across connected services.

Give your team more capacity

Reduce the preparation, checking and follow-up around recurring work.

Connect AI use to delivered work

Follow AI activity into projects, code and business results.
Quick links
Flowstate / People + AI Talk through your priorities
Documentation
Get help
Docs / Flowstate Helm

See what AI is used for

Spend says what AI cost. Work, Projects and Engineering say what it was used for. Each one reads a different connection, so connect the ones you need.

PageWhat it showsNeeds
WorkWhat people worked on with AI, by kind of work, and which sessions still need a project.Conversation records from your AI services, through their compliance API
ProjectsWhich projects received AI work, and the sessions behind each one.Your project tool
EngineeringPull requests, merged changes and how much AI contributed to them.Your source control, such as GitHub

Read what people worked on

  1. Go to Work.
  2. Read AI sessions, how many are Linked to projects and how many are Awaiting attribution.
  3. Use What people worked on to see the kinds of work AI supported.
  4. Select a session to see who had it, with which tool, and what it cost.

See which projects AI went on

  1. Go to Projects.
  2. Read Projects with AI work and Attributed sessions.
  3. Select a project to see the sessions behind it.

Matching sessions to project tasks can take up to 24 hours. Session time is recorded time. It isn’t time saved.

See AI’s part in your code

  1. Go to Engineering.
  2. Read AI-assisted changes, Agent-authored changes, AI engineering cost and AI cost per merged change.
  3. Under What AI contributed, read the lines AI wrote, and how many of those people then edited.

Source control is enough to start. Connect your AI services too to see which changes AI helped with.

Before you connect

Each page shows an example first. Select Explore the example page → to look around with sample data. When you’re ready, select Connect and choose a service.

For conversation records, an admin of your AI service may need to switch on access to them. Usage and billing alone can’t show what a conversation was about. See Capture AI prompts and responses.

If something’s not right